Triple
T20800318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signal Hill National Historic Site |
E512020
|
entity |
| Predicate | hasStructureStyle |
P72006
|
FINISHED |
| Object | 19th-century defensive architecture |
—
|
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: 19th-century defensive architecture | Statement: [Signal Hill National Historic Site, hasStructureStyle, 19th-century defensive architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureStyle Context triple: [Signal Hill National Historic Site, hasStructureStyle, 19th-century defensive architecture]
-
A.
hasStructuralStyle
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular architectural or structural design style.
-
B.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
C.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
D.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
E.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b014648190a1133836b36c26cd |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.