Triple
T14912412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HiFi Eastern Gateway |
E371293
|
entity |
| Predicate | isTypeOfStructure |
P841
|
FINISHED |
| Object | decorative arch |
—
|
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: decorative arch | Statement: [HiFi Eastern Gateway, isTypeOfStructure, decorative arch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypeOfStructure Context triple: [HiFi Eastern Gateway, isTypeOfStructure, decorative arch]
-
A.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
C.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
D.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
E.
hasStructureCode
Indicates that an entity is associated with a specific structural identifier or code that defines its organization or configuration.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61d75008190b6f9a1a38137836f |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:27 a.m.