Triple
T32173951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crossing |
E821784
|
entity |
| Predicate | releaseDatePart1 |
P172366
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [The Crossing, releaseDatePart1, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseDatePart1 Context triple: [The Crossing, releaseDatePart1, 2014]
-
A.
releaseDatePartOne
chosen
Indicates the date on which the first part or initial installment of something (such as a work, product, or series) is officially released.
-
B.
releaseDatePartTwo
Indicates the date on which the second part or installment of something (e.g., a work, product, or event) is released.
-
C.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
D.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
E.
releasedUnder
Indicates that one entity is made available, distributed, or published according to the terms, conditions, or authority specified by another entity (such as a license, label, or governing framework).
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 12:34 a.m.