Triple
T23840231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria–Italy |
E590965
|
entity |
| Predicate | disputeStatusOnSouthTyrol |
P110269
|
FINISHED |
| Object | largely resolved |
—
|
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: largely resolved | Statement: [Austria–Italy, disputeStatusOnSouthTyrol, largely resolved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeStatusOnSouthTyrol Context triple: [Austria–Italy, disputeStatusOnSouthTyrol, largely resolved]
-
A.
disputeStatus
chosen
Indicates the current state or condition of a disagreement or conflict between parties.
-
B.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
-
C.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
D.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
-
E.
disputeResolvedBy
Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c886aab081909ad896abe383afb9 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:08 p.m.