Triple
T34194848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Mustang Boss 302 (Coyote-based RoadRunner variant) |
E877212
|
entity |
| Predicate | engineCodeName |
P44382
|
FINISHED |
| Object | RoadRunner |
—
|
NE NERFINISHED |
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: RoadRunner | Statement: [Ford Mustang Boss 302 (Coyote-based RoadRunner variant), engineCodeName, RoadRunner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineCodeName Context triple: [Ford Mustang Boss 302 (Coyote-based RoadRunner variant), engineCodeName, RoadRunner]
-
A.
engineCode
chosen
Indicates a relationship where an entity is associated with a specific engine identification code or designation.
-
B.
engineName
Indicates the specific name assigned to an engine associated with an entity.
-
C.
hardwareCodename
Indicates that one entity is the internal or code name assigned to a particular hardware product or component.
-
D.
projectCodeName
Indicates that an entity (such as a project or initiative) is associated with a specific internal or informal code name used to identify it.
-
E.
testCodeName
Indicates that an entity is identified or referred to by a specific test code name.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:55 a.m.