Triple
T34448313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Wheel |
E884290
|
entity |
| Predicate | alignmentAxes |
P167133
|
FINISHED |
| Object | law–chaos |
—
|
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: law–chaos | Statement: [Great Wheel, alignmentAxes, law–chaos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentAxes Context triple: [Great Wheel, alignmentAxes, law–chaos]
-
A.
alignmentShape
Indicates that one entity’s shape is arranged, oriented, or matched in position relative to another entity’s shape.
-
B.
alignmentComponents
Indicates that one entity is composed of or associated with specific subparts or elements that together form its overall alignment.
-
C.
alignmentControl
Indicates that one entity manages, adjusts, or enforces the positional or structural alignment of another entity.
-
D.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
-
E.
alignmentSystem
chosen
Indicates the system or framework that defines how entities are categorized or oriented along a particular alignment or value scale.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7194f81b081909193f38ab428e52b |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.