Triple
T21706529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ionian order |
E535783
|
entity |
| Predicate | moreSlenderThan |
P11452
|
FINISHED |
| Object | Doric order |
—
|
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: Doric order | Statement: [Ionian order, moreSlenderThan, Doric order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreSlenderThan Context triple: [Ionian order, moreSlenderThan, Doric order]
-
A.
smallerThan
chosen
Indicates that one entity has a strictly lesser size, dimension, or magnitude than another entity.
-
B.
isNarrowestPartOf
Indicates that one entity constitutes the slimmest or most constricted section within the extent or structure of another entity.
-
C.
isSmall
Indicates that one entity has a size that is relatively small, either in absolute terms or compared to a reference standard or another entity.
-
D.
sizeRestriction
Indicates that there is a limitation or constraint on the allowable size or dimensions of something in the relationship.
-
E.
isNarrow
Indicates that something has a small width or limited breadth relative to a reference or context.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb52f64c48190b5d59561999e922f |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.