Triple
T34949445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jameson |
E1007946
|
entity |
| Predicate | aboriginalCommunity |
P26570
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jameson, aboriginalCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aboriginalCommunity Context triple: [Jameson, aboriginalCommunity, true]
-
A.
indigenousCommunity
chosen
Indicates that an entity is an indigenous community, i.e., a group with historical, cultural, and ancestral ties to a specific territory predating external or colonial societies.
-
B.
nonIndigenousCommunityOf
Indicates that the subject is a community that is not Indigenous in relation to the referenced place, group, or context.
-
C.
aboriginalCommunitySignificance
Indicates that something holds cultural, historical, or spiritual importance for an Aboriginal community.
-
D.
metIndigenousPeople
Indicates that an entity has encountered or come into contact with Indigenous people.
-
E.
broaderIndigenousGrouping
Indicates that one indigenous group is a broader, more inclusive grouping that encompasses another, more specific indigenous group.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782ccb1ec8190a15e00c9e678e5da |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.