Triple
T32158832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Isabel Lighthouse |
E821370
|
entity |
| Predicate | wasDeactivated |
P95601
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Port Isabel Lighthouse, wasDeactivated, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDeactivated Context triple: [Port Isabel Lighthouse, wasDeactivated, early 20th century]
-
A.
deactivatedIn
Indicates that an entity has been turned off, disabled, or made inactive within a specified context, system, or time frame.
-
B.
deactivatedAt
chosen
Indicates the time or date at which an entity was disabled, turned off, or made inactive.
-
C.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
D.
canBeDeactivatedBy
Indicates that one entity has the ability or means to deactivate or disable another entity.
-
E.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:32 a.m.