Triple
T23607708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumzari people |
E582941
|
entity |
| Predicate | accessToHomeland |
P153262
|
FINISHED |
| Object | primarily by boat |
—
|
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: primarily by boat | Statement: [Kumzari people, accessToHomeland, primarily by boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToHomeland Context triple: [Kumzari people, accessToHomeland, primarily by boat]
-
A.
hasHomeland
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
B.
recognizedHomelandsPolicy
Indicates that an authority formally acknowledges and accepts a specific homelands policy as valid or in effect.
-
C.
wasHomelandIn
Indicates that a location historically served as the homeland or place of origin for a specified group or entity.
-
D.
viewOfHomeland
Indicates a perspective, opinion, or emotional attitude that an entity holds toward its homeland.
-
E.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
- F. None of above. chosen
Provenance (4 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0f107048190b81eade6a50db2da |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:44 p.m.