Triple
T31825090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indy |
E812367
|
entity |
| Predicate | originatesFromWorkReleasedIn |
P143706
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Indy, originatesFromWorkReleasedIn, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromWorkReleasedIn Context triple: [Indy, originatesFromWorkReleasedIn, 2018]
-
A.
presentInWorkReleasedIn
Indicates that something appears within a work (e.g., book, film, album) that has been released in a specified year or time period.
-
B.
originatedInWorkBy
Indicates that something was created, derived, or first appeared within a particular work produced by a specific creator.
-
C.
basedInWorkReleaseYear
chosen
Indicates that an entity is based in, or derived from, a work that was released in a specified year.
-
D.
createdForWorkReleasedInYear
Indicates that something was created specifically for a work that was released in a particular year.
-
E.
workProducedBy
Indicates that a particular work (such as a creation, product, or result) was created, generated, or authored by a specific agent or 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
Created at: April 30, 2026, 11:46 p.m.