Triple
T34221775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kippure |
E877939
|
entity |
| Predicate | operatorOfMast |
P199317
|
FINISHED |
| Object | 2RN |
—
|
NE NERFINISHED |
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: 2RN | Statement: [Kippure, operatorOfMast, 2RN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOfMast Context triple: [Kippure, operatorOfMast, 2RN]
-
A.
coreOperator
Indicates that an entity functions as a primary or central operator responsible for executing or managing a core operation within a system or process.
-
B.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
missionOperator
Indicates that one entity is responsible for operating, managing, or controlling a mission involving another entity.
-
D.
servesAsOperatorOf
chosen
Indicates that one entity functions as the operator or operating agent responsible for running, controlling, or managing another entity.
-
E.
operatorStart
Indicates the point in time or event at which an operator begins performing an action or process.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00ab25c5b48190ad07ff508392ef56 |
completed | May 10, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_6a00a8a5cfc48190bbe97fb2bbd1b947 |
completed | May 10, 2026, 3:47 p.m. |
Created at: May 1, 2026, 1:55 a.m.