Triple
T9504607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Württemberg Army |
E229230
|
entity |
| Predicate | subordinationAfter |
P47649
|
FINISHED |
| Object | German unification |
—
|
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 unification | Statement: [Württemberg Army, subordinationAfter, German unification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subordinationAfter Context triple: [Württemberg Army, subordinationAfter, German unification]
-
A.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
B.
laterUnderRuleOf
chosen
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
-
C.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
D.
notSubordinateTo
Indicates that one entity is not in a lower-ranking, subordinate, or reporting position to another entity within a hierarchy or organizational structure.
-
E.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9850fe6c8190a5a96cfae12562c6 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.