Triple
T16395780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allison 501 |
E398174
|
entity |
| Predicate | firstRunPeriod |
P74271
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Allison 501, firstRunPeriod, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunPeriod Context triple: [Allison 501, firstRunPeriod, 1950s]
-
A.
firstRunTimePeriod
chosen
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
-
B.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
C.
firstRunProducer
Indicates that the producer is responsible for the initial or original run of a production, such as the first airing, release, or performance.
-
D.
firstRunViewership
Indicates the number of viewers who watched a program during its initial (first) broadcast or release.
-
E.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326462298819087091dc935f0f916 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.