Triple
T2378062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayes Theater |
E46244
|
entity |
| Predicate | hasFacadeDetail |
P31480
|
FINISHED |
| Object | classical ornamentation |
—
|
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: classical ornamentation | Statement: [Hayes Theater, hasFacadeDetail, classical ornamentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacadeDetail Context triple: [Hayes Theater, hasFacadeDetail, classical ornamentation]
-
A.
facadeFeature
chosen
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
B.
hasFacet
Indicates that an entity possesses a particular aspect, side, or dimension as one of its distinguishable parts or characteristics.
-
C.
hasLEDFacade
Indicates that an entity features a facade equipped with LED lighting or LED display technology.
-
D.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
E.
hasImplementationDetail
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.