Triple
T38587212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Heroes statues |
E932371
|
entity |
| Predicate | commemoratesFaction |
P140946
|
FINISHED |
| Object | Alliance |
—
|
NE NERFINISHED |
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: Alliance | Statement: [Valley of Heroes statues, commemoratesFaction, Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesFaction Context triple: [Valley of Heroes statues, commemoratesFaction, Alliance]
-
A.
commemoratesField
Indicates that one entity serves to honor, remember, or mark the significance of another entity, event, or achievement.
-
B.
commemoratesAlliance
chosen
Indicates a relationship where one entity honors or marks the memory of an alliance formed between two or more parties.
-
C.
commemoratesUnit
Indicates that one entity serves as a memorial or tribute recognizing, honoring, or remembering a specific unit.
-
D.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
E.
commemoratedGroup
Indicates that a group is honored, remembered, or recognized, typically through a memorial, event, or other commemorative act.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:32 p.m.