Triple
T14017430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia–China relations |
E337238
|
entity |
| Predicate | mainLanguageInDiplomacy |
P18093
|
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: [Australia–China relations, mainLanguageInDiplomacy, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLanguageInDiplomacy Context triple: [Australia–China relations, mainLanguageInDiplomacy, English]
-
A.
languageOfNegotiation
chosen
Indicates that a specified language is used as the medium of communication during a negotiation between parties.
-
B.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
C.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
D.
languageOfPoliticalContext
Indicates the language in which a given political context, discourse, or situation is expressed or conducted.
-
E.
languageOfDebate
Indicates that a specified language is the one used for conducting a particular debate.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3b5b088190a58715779d2c46a6 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.