Triple
T28291816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur |
E713446
|
entity |
| Predicate | appearsInCountrySetting |
P117234
|
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: [Arthur, appearsInCountrySetting, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInCountrySetting Context triple: [Arthur, appearsInCountrySetting, Australia]
-
A.
isSetInCountry
chosen
Indicates that something (such as an event, story, or scene) takes place within the geographical or political boundaries of a specified country.
-
B.
displayedInCountry
Indicates that something is shown, exhibited, or made visible within the boundaries of a specified country.
-
C.
usedInCountryOrRegion
Indicates that something (such as an item, concept, or practice) is utilized or applied within a specified country or region.
-
D.
includesPresentCountry
Indicates that an entity (such as a region, organization, or grouping) currently contains or encompasses a specified country within its present composition or membership.
-
E.
presentInCountries
Indicates that the subject entity exists, operates, or is available within the specified countries.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 11:29 p.m.