Triple
T5353305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carr Lightship |
E102627
|
entity |
| Predicate | lightVisibility |
P11173
|
FINISHED |
| Object | visible to passing ships at sea |
—
|
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: visible to passing ships at sea | Statement: [North Carr Lightship, lightVisibility, visible to passing ships at sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightVisibility Context triple: [North Carr Lightship, lightVisibility, visible to passing ships at sea]
-
A.
lightLevel
Indicates the intensity or amount of light present in a given context or environment.
-
B.
lightRange
chosen
Indicates the distance or area over which a light source effectively emits or illuminates.
-
C.
illuminationCondition
Indicates the lighting or brightness conditions under which an event, observation, or interaction takes place.
-
D.
isIlluminatedAtNight
Indicates that an entity receives or emits sufficient light to be visibly illuminated during nighttime conditions.
-
E.
surfaceBrightnessClass
Indicates the qualitative classification of how bright an extended object (such as a galaxy) appears per unit area on the sky.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86149774819084049a8785e3f2e0 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.