Triple
T20224760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chartres-style labyrinth |
E495347
|
entity |
| Predicate | hasGeometricStructure |
P25627
|
FINISHED |
| Object | concentric rings |
—
|
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: concentric rings | Statement: [Chartres-style labyrinth, hasGeometricStructure, concentric rings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeometricStructure Context triple: [Chartres-style labyrinth, hasGeometricStructure, concentric rings]
-
A.
hasGeometry
chosen
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
B.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
C.
hasRealStructure
Indicates that an abstract object or system is endowed with a concrete, well-defined mathematical or physical structure that makes it realizable or interpretable in a real-world or formal model.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd8f1948190adbb947a7870bb43 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.