Triple
T31552411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubble Light |
E805039
|
entity |
| Predicate | hasSignalRange |
P191700
|
FINISHED |
| Object | approximately 13 nautical miles |
—
|
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: approximately 13 nautical miles | Statement: [Nubble Light, hasSignalRange, approximately 13 nautical miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignalRange Context triple: [Nubble Light, hasSignalRange, approximately 13 nautical miles]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasSoundingRange
Indicates the extent or span of pitches over which something (typically an instrument or voice) can produce sound.
-
C.
hasSignalBox
Indicates that one entity is equipped with, contains, or is associated with a railway signal box used to control train movements.
-
D.
hasGateRange
Indicates the range of values or interval within which a gate or gating parameter is valid or operates.
-
E.
hasSignalReadout
Indicates that an entity provides or is associated with a measurable signal output that can be read or recorded.
- F. None of above. chosen
Provenance (4 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 30, 2026, 10:11 p.m.