Triple
T31731193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinthian order |
E809862
|
entity |
| Predicate | hasCapitalShape |
P82774
|
FINISHED |
| Object | bell-shaped core |
—
|
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: bell-shaped core | Statement: [Corinthian order, hasCapitalShape, bell-shaped core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalShape Context triple: [Corinthian order, hasCapitalShape, bell-shaped core]
-
A.
hasDistinctiveShape
chosen
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
B.
hasLetterforms
Indicates a relationship where one entity possesses or includes specific letterforms as part of its written or typographic representation.
-
C.
hasCapitalFeature
Indicates that one entity possesses or is characterized by a primary or most important feature represented by the other entity.
-
D.
hasCapitalOnOneSide
Indicates that one entity has its capital city located on one side (e.g., bank, shore, border) of the other entity.
-
E.
hasBillShape
Indicates that one entity has a bill whose shape matches the specified form or category.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 30, 2026, 11:21 p.m.