Triple
T23840212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria–Italy |
E590965
|
entity |
| Predicate | austrianConsulateInItaly |
P153837
|
FINISHED |
| Object | Milan |
—
|
NE NERFINISHED |
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: Milan | Statement: [Austria–Italy, austrianConsulateInItaly, Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: austrianConsulateInItaly Context triple: [Austria–Italy, austrianConsulateInItaly, Milan]
-
A.
hasConsulateOfCroatiaIn
Indicates that a location hosts an official consulate representing Croatia.
-
B.
resultForAustria
Indicates that a particular outcome, performance, or result is specifically associated with Austria.
-
C.
hasConsulateOfSwitzerlandIn
Indicates that a consulate representing Switzerland is located in a specified place.
-
D.
AustrianDesignation
Indicates that an entity has an official designation, title, or status specifically within the Austrian context (e.g., by Austrian law, administration, or standards).
-
E.
involvedUnitAustrian
Indicates that an Austrian military or organizational unit was involved as a participant in the referenced event or activity.
- 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_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. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:08 p.m.