Triple
T29106945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igo |
E736785
|
entity |
| Predicate | hasCaptureMechanic |
P191313
|
FINISHED |
| Object | surrounding opponent stones |
—
|
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: surrounding opponent stones | Statement: [Igo, hasCaptureMechanic, surrounding opponent stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptureMechanic Context triple: [Igo, hasCaptureMechanic, surrounding opponent stones]
-
A.
hasTriggerMechanism
Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
-
B.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
C.
capturableWith
chosen
Indicates that one entity can be captured or taken control of using a specified tool, method, or resource.
-
D.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
E.
haveHighLevelMechanism
Indicates that an entity possesses or is associated with a high-level, abstract mechanism explaining how something works or occurs.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 28, 2026, 11:16 a.m.