Triple
T35029915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazon-Nistrim |
E1010448
|
entity |
| Predicate | resourceConcern |
P64698
|
FINISHED |
| Object | competition for water and technology |
—
|
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: competition for water and technology | Statement: [Kazon-Nistrim, resourceConcern, competition for water and technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceConcern Context triple: [Kazon-Nistrim, resourceConcern, competition for water and technology]
-
A.
concernsProvision
Indicates a relationship where something is about, deals with, or relates to the supplying or making available of resources, services, or necessities.
-
B.
concernsRole
Indicates that something is related or pertains specifically to a particular role or function held by an entity.
-
C.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
D.
targetConcern
chosen
Indicates that something is the specific issue, problem, or subject that is the focus of attention, action, or consideration.
-
E.
concernedRite
Indicates that a rite, ritual, or ceremonial act is the focus or subject of concern, involvement, or relevance in the relationship.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.