Triple
T27952798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North, East, South, West |
E703472
|
entity |
| Predicate | usesGeometricForms |
P73092
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [North, East, South, West, usesGeometricForms, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGeometricForms Context triple: [North, East, South, West, usesGeometricForms, true]
-
A.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
B.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
C.
shapeType
Indicates the specific geometric form or category that characterizes an entity’s shape.
-
D.
geometricSetting
Indicates the spatial or geometric context within which an object, relation, or event is defined or occurs.
-
E.
geometricConfiguration
chosen
Indicates the specific spatial arrangement and relationships among parts or elements within a geometric structure.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:25 p.m.