Triple
T25433516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domineering |
E637317
|
entity |
| Predicate | hasPieceShape |
P158503
|
FINISHED |
| Object | 1×2 rectangle |
—
|
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: 1×2 rectangle | Statement: [Domineering, hasPieceShape, 1×2 rectangle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPieceShape Context triple: [Domineering, hasPieceShape, 1×2 rectangle]
-
A.
hasHoleShape
Indicates that an entity possesses a hole or opening characterized by a specific geometric or structural shape.
-
B.
hasHemShape
Indicates that an item possesses a specific form or contour of its hem or lower edge.
-
C.
hasPitShape
Indicates that an entity possesses or exhibits a particular pit-like shape or form.
-
D.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
E.
hasBillShape
Indicates that one entity has a bill whose shape matches the specified form or category.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dd99f88190848a5bbee795aa17 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:59 p.m.