Triple
T31617254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Men from Shiloh |
E806793
|
entity |
| Predicate | hasAnthologyStyleStorytelling |
P71401
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Men from Shiloh, hasAnthologyStyleStorytelling, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnthologyStyleStorytelling Context triple: [The Men from Shiloh, hasAnthologyStyleStorytelling, yes]
-
A.
hasAnthologyFormat
chosen
Indicates that an entity is presented or structured in the form of an anthology (a collection of distinct works or pieces).
-
B.
isAnthologySegmentOf
Indicates that one work or segment is a constituent part or episode within a larger anthology work.
-
C.
hasAnthologyRelation
Indicates that there is a relationship between entities based on their inclusion in, contribution to, or association with the same anthology or collected work.
-
D.
hasStandaloneTales
Indicates that an entity includes or is associated with independent, self-contained stories that can be understood without relying on a larger narrative.
-
E.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 30, 2026, 10:39 p.m.