Triple
T8945745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuscan order |
E213216
|
entity |
| Predicate | rankWithinOrders |
P17947
|
FINISHED |
| Object | most plain of the classical orders |
—
|
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: most plain of the classical orders | Statement: [Tuscan order, rankWithinOrders, most plain of the classical orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinOrders Context triple: [Tuscan order, rankWithinOrders, most plain of the classical orders]
-
A.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
B.
hasRankOrder
chosen
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
C.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
-
D.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
E.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66dd00c481908ff20fd66c1954cc |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.