Triple
T5647892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge American Cemetery |
E124427
|
entity |
| Predicate | useDuringWar |
P30719
|
FINISHED |
| Object | temporary American military cemetery |
—
|
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: temporary American military cemetery | Statement: [Cambridge American Cemetery, useDuringWar, temporary American military cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useDuringWar Context triple: [Cambridge American Cemetery, useDuringWar, temporary American military cemetery]
-
A.
usedInWar
Indicates that something (such as a resource, technology, or strategy) was employed as part of military activities or conflict in a war.
-
B.
operatorDuringWar
Indicates that an entity operated or was active in its role during a time of war.
-
C.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
D.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
E.
wartimeUse
chosen
Indicates that something is used or employed during a period of war or armed conflict.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d1534c8190ac4828e44300fb91 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.