Triple
T870554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Powers |
E18801
|
entity |
| Predicate | surrenderOfMember |
P4666
|
FINISHED |
| Object | German Empire 1918 |
—
|
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: German Empire 1918 | Statement: [Central Powers, surrenderOfMember, German Empire 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderOfMember Context triple: [Central Powers, surrenderOfMember, German Empire 1918]
-
A.
surrenderingParty
chosen
Indicates the party that yields control, rights, or possession to another in a surrender or transfer arrangement.
-
B.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
C.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
D.
surrenderEvent
Indicates an event in which one party yields or gives up control, rights, or resistance to another party.
-
E.
countrySurrendering
Indicates that one country formally yields to another country’s authority or control, typically ending a conflict or war.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac94d5ac81909feee876696da589 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.