Triple
T136464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Big Three automakers |
E2757
|
entity |
| Predicate | timePeriodOfDominance |
P5898
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Detroit Big Three automakers, timePeriodOfDominance, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfDominance Context triple: [Detroit Big Three automakers, timePeriodOfDominance, 20th century]
-
A.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
B.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
C.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
-
D.
governedForMostOfPeriodSince
Indicates that one entity has held governing authority over another for the majority of a specified time period since a given starting point.
-
E.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a4edf081908c494c8370c76b9a |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2570f45bc81909ebba7ee5f602976 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.