Triple
T29106824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiqi |
E736783
|
entity |
| Predicate | stonePlacement |
P166338
|
FINISHED |
| Object | on the intersections of lines |
—
|
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: on the intersections of lines | Statement: [Weiqi, stonePlacement, on the intersections of lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stonePlacement Context triple: [Weiqi, stonePlacement, on the intersections of lines]
-
A.
stonePlacementSymbolism
Indicates the symbolic meaning or message conveyed by the way a stone is placed in relation to something or someone.
-
B.
stoneFunction
Indicates that something serves as the function, role, or purpose of a stone within a given context.
-
C.
stickPlacement
Indicates the spatial arrangement or positioning of a stick relative to other objects or a reference frame.
-
D.
stoneFitting
Indicates that one stone is shaped or positioned so that it fits securely and appropriately with another stone or within a designated stone structure.
-
E.
ballPlacement
Indicates the spatial positioning or arrangement of a ball relative to a reference point, object, or area.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661ba062881909fa3d7b23938e2ab |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:16 a.m.