Triple
T33843305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meriam people |
E867410
|
entity |
| Predicate | jurisdictionOfRecognition |
P132724
|
FINISHED |
| Object | Queensland |
—
|
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: Queensland | Statement: [Meriam people, jurisdictionOfRecognition, Queensland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurisdictionOfRecognition Context triple: [Meriam people, jurisdictionOfRecognition, Queensland]
-
A.
countryOfRecognition
Indicates the country that formally recognizes, acknowledges, or grants official status to a given entity.
-
B.
countryOfJurisdiction
Indicates the country whose legal authority or jurisdiction governs or applies to a given entity, action, or arrangement.
-
C.
legalStatusRecognizedIn
chosen
Indicates that an entity’s legal status is officially acknowledged or valid within a specified jurisdiction or legal system.
-
D.
canonicalJurisdictionOf
Indicates that one entity holds official legal or ecclesiastical authority over another entity or domain as its recognized jurisdiction.
-
E.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700516f688190aa62ea1ee73ddfeb |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.