Triple
T18947018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria and Czech Republic |
E463539
|
entity |
| Predicate | hasEmbassyInEachOther |
P12096
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Austria and Czech Republic, hasEmbassyInEachOther, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmbassyInEachOther Context triple: [Austria and Czech Republic, hasEmbassyInEachOther, true]
-
A.
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.
-
B.
diplomaticRelation
Indicates a formal relationship of negotiation, communication, or representation between political entities, typically states or governments.
-
C.
diplomaticRelationBetween
Indicates the existence of a formal diplomatic relationship or ties between two political entities or states.
-
D.
hasConsulateOfUnitedStatesIn
Indicates that a consulate of the United States is located in the specified place.
-
E.
haveConsulates
Indicates that one country maintains consular offices or consulates within the territory of another country.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5402ad881908add559249278895 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.