Triple
T9226893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Fusion |
E221705
|
entity |
| Predicate | roleInLineup |
P18925
|
FINISHED |
| Object | core Ford passenger car in 2000s |
—
|
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: core Ford passenger car in 2000s | Statement: [Ford Fusion, roleInLineup, core Ford passenger car in 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLineup Context triple: [Ford Fusion, roleInLineup, core Ford passenger car in 2000s]
-
A.
positionInLineup
chosen
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
-
B.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
E.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9ecef48190b8aa0e316d07cec7 |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.