Triple
T9889631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banliang coin |
E181419
|
entity |
| Predicate | hasHoleShape |
P91630
|
FINISHED |
| Object | square |
—
|
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: square | Statement: [Banliang coin, hasHoleShape, square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHoleShape Context triple: [Banliang coin, hasHoleShape, square]
-
A.
hasHoleCount
Indicates that an entity possesses a specified number of holes.
-
B.
hasHoleName
Indicates that an entity (such as a golf course or layout) has a specific hole identified by a particular name.
-
C.
numberOfHoles
Indicates the count of holes associated with or present in a given entity.
-
D.
hasHoleNumberRange
Indicates that an entity is associated with a contiguous range of hole numbers, from a specified starting hole to an ending hole.
-
E.
hasTunnelShape
Indicates that something possesses a form or configuration resembling a tunnel, typically elongated, enclosed, and passage-like.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47be2988190811a99dc56ae542a |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:39 p.m.