Triple
T37458777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piloted Sky Golem |
E930864
|
entity |
| Predicate | hasBoardPresenceEffect |
P197040
|
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: [Piloted Sky Golem, hasBoardPresenceEffect, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoardPresenceEffect Context triple: [Piloted Sky Golem, hasBoardPresenceEffect, yes]
-
A.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
B.
hasOnboardEffects
Indicates that something produces effects or consequences specifically on board a vehicle, vessel, or similar platform.
-
C.
boardPresenceImpact
Indicates how the presence or composition of a board (e.g., directors or advisors) influences outcomes, performance, or decisions related to an entity.
-
D.
hasBoardComposition
Indicates that an entity has a specific structure or makeup of its governing board, such as the types or proportions of members who serve on it.
-
E.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69fe744e9ee081909b362fc8609bc744 |
completed | May 8, 2026, 11:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.