Triple
T9275491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Golden King |
E222935
|
entity |
| Predicate | refersToPersonPrimaryTheaterOfWar |
P87907
|
FINISHED |
| Object | Central Europe |
—
|
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: Central Europe | Statement: [The Golden King, refersToPersonPrimaryTheaterOfWar, Central Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPersonPrimaryTheaterOfWar Context triple: [The Golden King, refersToPersonPrimaryTheaterOfWar, Central Europe]
-
A.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
B.
foughtInCountry
Indicates that an entity participated in a fight, battle, or war that took place within the specified country.
-
C.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
D.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
E.
capturedInWar
Indicates that one entity was taken prisoner or seized by another entity as a result of armed conflict or wartime actions.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07c71b5c8190b5b7b5ab4224e9d3 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:34 p.m.