Triple
T15930773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V8 engine |
E386317
|
entity |
| Predicate | hasAlternativeBankAngle |
P80550
|
FINISHED |
| Object | 60 degrees |
—
|
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: 60 degrees | Statement: [V8 engine, hasAlternativeBankAngle, 60 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeBankAngle Context triple: [V8 engine, hasAlternativeBankAngle, 60 degrees]
-
A.
supportsAngleModes
Indicates that one entity provides functionality for handling or operating in multiple angle measurement modes (such as degrees, radians, or gradians) for another entity or context.
-
B.
hasAlternativeMultiplierChoice
Indicates that an entity is associated with one or more alternative options for a multiplier that can be chosen instead of a default value.
-
C.
hasBankCharacteristic
chosen
Indicates that a bank possesses a particular attribute, feature, or quality.
-
D.
hasAlternateCut
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
-
E.
hasWireAngle
Indicates that one entity has a wire oriented or positioned at a specific angle relative to another reference or component.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.