Triple
T796165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolinian |
E17025
|
entity |
| Predicate | statusInCNMI |
P19234
|
FINISHED |
| Object | recognized indigenous language |
—
|
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: recognized indigenous language | Statement: [Carolinian, statusInCNMI, recognized indigenous language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInCNMI Context triple: [Carolinian, statusInCNMI, recognized indigenous language]
-
A.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
B.
statusInMaryland
Indicates that an entity holds a particular legal, regulatory, or operational status specifically within the jurisdiction of Maryland.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
E.
stateRock
Indicates that an entity is in a solid, rock-like physical state or condition.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b172e88190a26d31c9075b81fb |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a5edd0248190bd0240e5b3e67c71 |
completed | March 1, 2026, 8:47 p.m. |
Created at: March 1, 2026, 7:38 p.m.