Triple
T22201052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Lights |
E548682
|
entity |
| Predicate | westernTowerStatus |
P82990
|
FINISHED |
| Object | deactivated |
—
|
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: deactivated | Statement: [Two Lights, westernTowerStatus, deactivated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernTowerStatus Context triple: [Two Lights, westernTowerStatus, deactivated]
-
A.
towerStatus
chosen
Indicates the current operational or structural condition of a tower within a given system or context.
-
B.
lighthouseStatus
Indicates the operational condition or state (e.g., active, inactive, under maintenance) of a lighthouse at a given time.
-
C.
headquartersStatus
Indicates the role or designation of a location in relation to serving as an organization’s headquarters (e.g., primary, regional, former).
-
D.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
-
E.
towerManagedBy
Indicates that a particular tower is under the control, supervision, or administrative responsibility of a specified managing 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aeb16348190a34f96b47e01c8cf |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.