Triple
T31336868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-twin |
E799197
|
entity |
| Predicate | hasBalanceCharacteristic |
P274
|
FINISHED |
| Object | good primary balance for 90-degree V-twin |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: good primary balance for 90-degree V-twin | Statement: [L-twin, hasBalanceCharacteristic, good primary balance for 90-degree V-twin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalanceCharacteristic Context triple: [L-twin, hasBalanceCharacteristic, good primary balance for 90-degree V-twin]
-
A.
hasOnlineBalanceCheck
Indicates that an entity provides the capability to check a balance via an online interface or service.
-
B.
hasBankCharacteristic
Indicates that a bank possesses a particular attribute, feature, or quality.
-
C.
balancesWith
Indicates that two entities are in a state of equilibrium or mutual offset, such that each counterbalances or matches the other in a specified context.
-
D.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
E.
hasMaximumBalanceLimit
Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 29, 2026, 9:16 p.m.