Triple
T28107670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari 053 |
E710404
|
entity |
| Predicate | regulationDisplacementLimit |
P84064
|
FINISHED |
| Object | 3.0 L |
—
|
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: 3.0 L | Statement: [Ferrari 053, regulationDisplacementLimit, 3.0 L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationDisplacementLimit Context triple: [Ferrari 053, regulationDisplacementLimit, 3.0 L]
-
A.
treatyDisplacementLimit
Indicates that a treaty specifies a maximum allowable level or extent of displacement resulting from actions governed by that agreement.
-
B.
hasMaxDisplacement
chosen
Indicates the maximum distance or extent to which something can move or be displaced from its original position.
-
C.
displacementRate
Indicates the rate at which an entity’s position changes over time relative to a reference point or frame.
-
D.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
E.
maximumTonnageLimitedBy
Indicates that the maximum allowable tonnage of one entity is constrained or capped by the capacity or limit specified by another entity.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 9:09 p.m.