Triple
T37462705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunkeeper Tarim |
E930957
|
entity |
| Predicate | boardWideEffect |
P159359
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Sunkeeper Tarim, boardWideEffect, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardWideEffect Context triple: [Sunkeeper Tarim, boardWideEffect, Yes]
-
A.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
-
B.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
C.
bustEffect
Indicates an action or event that causes something to fail, collapse, or be ruined, often abruptly or disastrously.
-
D.
sideEffect
Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
-
E.
canonicalEffect
chosen
Indicates the standard or primary effect that an action, event, or entity is typically understood to produce.
- 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_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.