Triple
T31617264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Men from Shiloh |
E806793
|
entity |
| Predicate | featuresMoreLocationShooting |
P202525
|
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, featuresMoreLocationShooting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMoreLocationShooting Context triple: [The Men from Shiloh, featuresMoreLocationShooting, yes]
-
A.
featuresLocation
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
B.
featuresTreasureHunt
Indicates that something includes or offers a treasure hunt activity or experience.
-
C.
sceneFeature
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
-
D.
featureOfInterest
Indicates the entity or object that is the primary subject or focus of the described observation, measurement, or analysis.
-
E.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_6a008d5fe63c8190ab4f5a31c249c674 |
completed | May 10, 2026, 1:51 p.m. |
Created at: April 30, 2026, 10:39 p.m.