Triple
T31463235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | asf |
E802659
|
entity |
| Predicate | representsLanguageUsedIn |
P192365
|
FINISHED |
| Object | Australia |
—
|
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: Australia | Statement: [asf, representsLanguageUsedIn, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsLanguageUsedIn Context triple: [asf, representsLanguageUsedIn, Australia]
-
A.
representsLanguagesOf
chosen
Indicates that one entity specifies or lists the languages associated with, used by, or characteristic of another entity.
-
B.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
-
C.
hasRepresentativeLanguage
Indicates that an entity is associated with a language that serves as its primary or officially recognized means of representation or communication.
-
D.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
E.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 30, 2026, 9:21 p.m.