Triple
T37458033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totemic Call |
E930847
|
entity |
| Predicate | boardPosition |
P189498
|
FINISHED |
| Object | Summons to Owner’s Side |
—
|
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: Summons to Owner’s Side | Statement: [Totemic Call, boardPosition, Summons to Owner’s Side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardPosition Context triple: [Totemic Call, boardPosition, Summons to Owner’s Side]
-
A.
positionInNotation
Indicates the specific place or index that an element occupies within a given ordered notation or representation.
-
B.
ballPlacement
Indicates the spatial positioning or arrangement of a ball relative to a reference point, object, or area.
-
C.
whiteDiscPosition
Indicates the spatial location or coordinates where the white disc is currently situated.
-
D.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
E.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:17 p.m.