Triple
T29120115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reason |
E737155
|
entity |
| Predicate | hasAlternativeTitleStyle |
P180520
|
FINISHED |
| Object | "Reason" (short story) |
—
|
NE NERFINISHED |
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: "Reason" (short story) | Statement: [Reason, hasAlternativeTitleStyle, "Reason" (short story)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeTitleStyle Context triple: [Reason, hasAlternativeTitleStyle, "Reason" (short story)]
-
A.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
B.
hasAlternativeTitleCombination
Indicates that an entity is associated with one or more alternative titles considered together as a specific combination or set.
-
C.
hasAlternativeEditionTitle
Indicates that an entity has a different or variant title used in another edition of the same work.
-
D.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
-
E.
hasTitleHolderAlternativeName
Indicates that an entity serving as a title holder is known by an alternative or additional name.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 11:25 a.m.