Triple
T396177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Mustang |
E8987
|
entity |
| Predicate | notableGeneration |
P12591
|
FINISHED |
| Object | first generation (1965–1973) |
—
|
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: first generation (1965–1973) | Statement: [Ford Mustang, notableGeneration, first generation (1965–1973)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGeneration Context triple: [Ford Mustang, notableGeneration, first generation (1965–1973)]
-
A.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
notableDescent
Indicates a genealogical relationship where one entity is a descendant of another in a way considered historically, culturally, or socially significant.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.