Triple
T7980825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Reversi |
E185564
|
entity |
| Predicate | turnStructure |
P68186
|
FINISHED |
| Object | alternating turns between players |
—
|
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: alternating turns between players | Statement: [Internet Reversi, turnStructure, alternating turns between players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnStructure Context triple: [Internet Reversi, turnStructure, alternating turns between players]
-
A.
turns
Indicates a change in orientation, direction, or state initiated by one entity affecting itself or another entity.
-
B.
roundsStructure
chosen
Indicates that one entity defines or specifies the organization, sequence, or format of rounds within a process, event, or system.
-
C.
turnedPro
Indicates that an individual transitioned from amateur status to professional status in a particular field or activity.
-
D.
turnsIn
Indicates that an entity submits or hands over something, typically work or an item, to another party or authority.
-
E.
currentStructure
Indicates that an entity is the present or active structural configuration or organization 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c274ce48190854d389d43ce14b8 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.