Triple
T13438807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hôtel de Crillon |
E320298
|
entity |
| Predicate | façadeOrder |
P88434
|
FINISHED |
| Object | Corinthian order on upper levels |
—
|
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: Corinthian order on upper levels | Statement: [Hôtel de Crillon, façadeOrder, Corinthian order on upper levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: façadeOrder Context triple: [Hôtel de Crillon, façadeOrder, Corinthian order on upper levels]
-
A.
displayOrder
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
B.
featuresOrder
Indicates that one entity specifies or determines the sequence or arrangement in which another entity’s features appear or are organized.
-
C.
airingOrder
Indicates the sequence in which items (such as episodes or installments) are broadcast or released to the public.
-
D.
orderHouse
Indicates that an entity requests or arranges the purchase or construction of a house.
-
E.
architecturalOrderUsed
chosen
Indicates that a particular architectural order (e.g., Doric, Ionic, Corinthian) is employed in the design or construction of a structure or its elements.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee5ec488190bd0c1e990dbd2bc2 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.