Triple
T31617260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Men from Shiloh |
E806793
|
entity |
| Predicate | hasDistinctTitleSequenceFrom |
P122852
|
FINISHED |
| Object | The Virginian |
—
|
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: The Virginian | Statement: [The Men from Shiloh, hasDistinctTitleSequenceFrom, The Virginian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctTitleSequenceFrom Context triple: [The Men from Shiloh, hasDistinctTitleSequenceFrom, The Virginian]
-
A.
hasMainTitleSequenceChange
chosen
Indicates that the main title sequence of a work has been altered or replaced between different versions or releases.
-
B.
isUniqueTitle
Indicates that a title is distinct and not shared by any other entity within the relevant context or collection.
-
C.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
D.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
E.
isTitledAfter
Indicates that one entity has been given a name or title derived from, in honor of, or referencing another 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 30, 2026, 10:39 p.m.