Triple
T3035136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William F. Cody |
E82989
|
entity |
| Predicate | hasPartInShow |
P10186
|
FINISHED |
| Object | staged reenactments of frontier battles |
—
|
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: staged reenactments of frontier battles | Statement: [William F. Cody, hasPartInShow, staged reenactments of frontier battles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInShow Context triple: [William F. Cody, hasPartInShow, staged reenactments of frontier battles]
-
A.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
B.
hasPartIn
chosen
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
C.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
D.
playedInSeason
Indicates that an entity (such as a player or participant) took part in or was active during a specific season.
-
E.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2a40b48190bfa7cdbb0fbd87f8 |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.