Triple
T10908749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-2 |
E257636
|
entity |
| Predicate | belongsToLineup |
P92683
|
FINISHED |
| Object | Ford postwar pickup truck lineup |
—
|
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: Ford postwar pickup truck lineup | Statement: [F-2, belongsToLineup, Ford postwar pickup truck lineup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToLineup Context triple: [F-2, belongsToLineup, Ford postwar pickup truck lineup]
-
A.
belongsToLine
chosen
Indicates that an entity is a member or component of a particular line or linear grouping.
-
B.
notableLineup
Indicates that an entity is recognized as part of a particularly significant or distinguished group, roster, or cast associated with another entity.
-
C.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
-
D.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
E.
associatedWithPlayers
Indicates a relationship in which one or more players are connected, linked, or otherwise involved with the referenced 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7706824d08190ba894d144cc6b3ba |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.