Triple
T26221616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria–Holy See relations |
E655777
|
entity |
| Predicate | hasEmbassyOfAustriaIn |
P12096
|
FINISHED |
| Object | Holy See |
—
|
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: Holy See | Statement: [Austria–Holy See relations, hasEmbassyOfAustriaIn, Holy See]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmbassyOfAustriaIn Context triple: [Austria–Holy See relations, hasEmbassyOfAustriaIn, Holy See]
-
A.
hasDiplomaticStaffFrom
Indicates that an entity has diplomatic personnel who originate from or represent another specified entity.
-
B.
hasConsulateOfUnitedStatesIn
Indicates that a consulate of the United States is located in the specified place.
-
C.
hasDiplomaticMission
chosen
Indicates that one entity maintains an official diplomatic representation, such as an embassy or mission, in the territory or jurisdiction of another entity.
-
D.
receivesDiplomaticAccreditationFrom
Indicates that an entity is formally recognized and accepted in an official diplomatic capacity by another entity that grants the accreditation.
-
E.
hasConsulateOfCroatiaIn
Indicates that a location hosts an official consulate representing Croatia.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d5060708190b3134a5e5a4ca850 |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:56 p.m.