Triple
T36956774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massive Chalice |
E914207
|
entity |
| Predicate | hasTacticalBattles |
P188492
|
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: [Massive Chalice, hasTacticalBattles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTacticalBattles Context triple: [Massive Chalice, hasTacticalBattles, yes]
-
A.
hasBattleScenes
Indicates that an entity (such as a work of fiction or media) contains scenes depicting battles or combat.
-
B.
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.
-
C.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
D.
numberOfMajorBattles
Indicates the total count of significant or major battles associated with an entity or event.
-
E.
hasTacticalSituation
Indicates that an entity is associated with, or is operating within, a specific tactical situation 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.