Triple
T7171571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germany–Belgium border |
E167210
|
entity |
| Predicate | stabilizationPurpose |
P31957
|
FINISHED |
| Object | stabilization of post–World War I 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: stabilization of post–World War I Europe | Statement: [Germany–Belgium border, stabilizationPurpose, stabilization of post–World War I Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stabilizationPurpose Context triple: [Germany–Belgium border, stabilizationPurpose, stabilization of post–World War I Europe]
-
A.
stabilizedBy
Indicates that an entity’s state, structure, or behavior is made more steady, secure, or resistant to change through the influence or support of another entity.
-
B.
stabilityReason
Indicates the factor, condition, or cause that accounts for why something remains stable or unchanged.
-
C.
stabilityPolicy
Indicates that a policy defines or influences the conditions under which a system, process, or arrangement remains stable over time.
-
D.
stabilityGoal
chosen
Indicates a relationship where an action, policy, or entity is aimed at achieving, maintaining, or enhancing stability in a given system or context.
-
E.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85ec718819085af59fadee9d22d |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.