Triple
T7295948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter-Allied Commission for Upper Silesia |
E164520
|
entity |
| Predicate | conflictTypeManaged |
P76063
|
FINISHED |
| Object | territorial dispute |
—
|
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: territorial dispute | Statement: [Inter-Allied Commission for Upper Silesia, conflictTypeManaged, territorial dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypeManaged Context triple: [Inter-Allied Commission for Upper Silesia, conflictTypeManaged, territorial dispute]
-
A.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
conflictRecognized
Indicates that a conflict between parties, interests, or actions has been identified and acknowledged.
-
C.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
D.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
E.
conflictResult
Indicates the outcome or consequence that arises from a particular conflict between entities.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8d0c6c8190b32cd08b9a5d96cc |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3 p.m.