Triple
T30756351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tritonian Ring |
E783093
|
entity |
| Predicate | containsBattleScenes |
P136051
|
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 Tritonian Ring, containsBattleScenes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBattleScenes Context triple: [The Tritonian Ring, containsBattleScenes, yes]
-
A.
hasBattleScenes
chosen
Indicates that an entity (such as a work of fiction or media) contains scenes depicting battles or combat.
-
B.
hasFightSceneWith
Indicates that two entities participate together in a fight scene or combat sequence.
-
C.
hasTacticalBattles
Indicates that there are one or more specific tactical-level combat engagements occurring between the related entities.
-
D.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
E.
coveredBattle
Indicates that an entity reported on, documented, or otherwise provided coverage of a particular battle or military engagement.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: April 29, 2026, 8:39 p.m.