Triple
T20004308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBMutableService |
E494410
|
entity |
| Predicate | initializer |
P138322
|
FINISHED |
| Object | init(type:primary:) |
—
|
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: init(type:primary:) | Statement: [CBMutableService, initializer, init(type:primary:)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initializer Context triple: [CBMutableService, initializer, init(type:primary:)]
-
A.
initiator
Indicates the entity that starts, triggers, or causes an action, event, or process to occur.
-
B.
initialStatus
Indicates the original or starting state assigned to an entity before any changes or updates occur.
-
C.
initialOperator
Indicates that an entity serves as the first or primary operator initiating a process, action, or operation involving another entity.
-
D.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
E.
initiative
Indicates that an entity takes the first step or leads in starting an action, project, or process without external prompting.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:33 p.m.