Triple
T19641360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of the United States in Canberra |
E471546
|
entity |
| Predicate | officialLanguageOfSendingState |
P136795
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Embassy of the United States in Canberra, officialLanguageOfSendingState, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialLanguageOfSendingState Context triple: [Embassy of the United States in Canberra, officialLanguageOfSendingState, English]
-
A.
respondentState
Indicates the state or jurisdiction in which the respondent is located, resides, or is legally associated.
-
B.
isStateMottoOf
Indicates that a phrase or sentence serves as the official state motto of a particular state.
-
C.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
-
D.
majorReceivingState
Indicates that an entity serves as the primary or principal recipient in a given relationship, transaction, or flow.
-
E.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6412224d481909524d7654a36d49b |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.