Triple
T22786706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Vicente Lighthouse |
E563985
|
entity |
| Predicate | hasBeacon |
P145497
|
FINISHED |
| Object | rotating light |
—
|
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: rotating light | Statement: [Point Vicente Lighthouse, hasBeacon, rotating light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeacon Context triple: [Point Vicente Lighthouse, hasBeacon, rotating light]
-
A.
hasBeaconCount
Indicates the number of beacons associated with or assigned to a given entity.
-
B.
beaconType
chosen
Indicates the specific kind or category of beacon associated with or used by an entity.
-
C.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
D.
hasNFC
Indicates that one entity possesses or supports Near Field Communication (NFC) capability in relation to another entity or context.
-
E.
hasBluetooth
Indicates that one entity is equipped with or supports Bluetooth connectivity.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c321f848190a4443aa6bb4e57d7 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.