Triple
T35429370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lac Courte Oreilles Reservation |
E1024010
|
entity |
| Predicate | hasTypeOfLand |
P41739
|
FINISHED |
| Object | trust land |
—
|
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: trust land | Statement: [Lac Courte Oreilles Reservation, hasTypeOfLand, trust land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfLand Context triple: [Lac Courte Oreilles Reservation, hasTypeOfLand, trust land]
-
A.
hasLandStatus
chosen
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
B.
hasLandClassification
Indicates the designated land-use or land-cover category assigned to a particular area or parcel.
-
C.
hasLandComponent
Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
-
D.
isInLandAreaType
Indicates that one entity is located within, or belongs to, a specified type of land area (such as urban, rural, coastal, or agricultural).
-
E.
hasLandholdingsIn
Indicates that an entity owns or controls land or property located within a specified geographic area.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 3, 2026, 4:03 p.m.