Triple
T29543484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche 961 |
E749566
|
entity |
| Predicate | displacementApprox |
P167010
|
FINISHED |
| Object | 2.8 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: 2.8 L | Statement: [Porsche 961, displacementApprox, 2.8 L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementApprox Context triple: [Porsche 961, displacementApprox, 2.8 L]
-
A.
displacementEstimate
Indicates an estimated amount or measure of how far something has moved or shifted from its original position.
-
B.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
C.
displacementRate
Indicates the rate at which an entity’s position changes over time relative to a reference point or frame.
-
D.
displacementOption
Indicates an available way or method by which something or someone can be moved, relocated, or shifted from one position or state to another.
-
E.
displacementVariant
Indicates a relationship where one entity is an alternative or modified form of another that differs specifically in its spatial position or displacement.
- F. None of above. chosen
Provenance (4 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 5:05 p.m.