Triple
T20522939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorain Lighthouse Foundation |
E503855
|
entity |
| Predicate | buildingTypePreserved |
P107428
|
FINISHED |
| Object | lighthouse |
—
|
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: lighthouse | Statement: [Lorain Lighthouse Foundation, buildingTypePreserved, lighthouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingTypePreserved Context triple: [Lorain Lighthouse Foundation, buildingTypePreserved, lighthouse]
-
A.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
-
C.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
D.
typeOfBuildingRestored
chosen
Indicates that a particular type of building has undergone restoration or renovation.
-
E.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f471f18819091e8a57161fe0225 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.