Triple
T37462908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primordial Drake |
E930962
|
entity |
| Predicate | boardControlRole |
P121597
|
FINISHED |
| Object | Board clear |
—
|
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: Board clear | Statement: [Primordial Drake, boardControlRole, Board clear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardControlRole Context triple: [Primordial Drake, boardControlRole, Board clear]
-
A.
boardControlTool
Indicates that an entity is a tool or mechanism used to manage, configure, or control a board or board-like system.
-
B.
controlStrategyRole
chosen
Indicates the specific function or responsibility an entity has within a control strategy or control-related process.
-
C.
boardPresenceRole
Indicates the specific role or capacity in which an entity serves on a board or governing body.
-
D.
cornerRole
Indicates the specific role or function an entity has in relation to a corner, such as positioning, responsibility, or interaction at that corner.
-
E.
oreControl
Indicates a relationship where one entity exercises authority or regulatory control over the extraction, management, or use of ore resources associated with another entity.
- 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_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:17 p.m.