Triple
T37460930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun |
E930913
|
entity |
| Predicate | strategyRole |
P84296
|
FINISHED |
| Object | Control finisher |
—
|
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: Control finisher | Statement: [C’Thun, strategyRole, Control finisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyRole Context triple: [C’Thun, strategyRole, Control finisher]
-
A.
strategicRoleIn
chosen
Indicates that one entity serves a strategic function, position, or importance within the context, operations, or objectives of another entity.
-
B.
developmentStrategyRole
Indicates the role or function an entity plays within a particular development strategy or plan.
-
C.
agencyRole
Indicates that one entity serves in a specific functional or organizational capacity on behalf of, or within, another entity (such as an agency, institution, or governing body).
-
D.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
E.
controlStrategyRole
Indicates the specific function or responsibility an entity has within a control strategy or control-related 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.