Triple
T35672122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratnagiri Lighthouse |
E1030747
|
entity |
| Predicate | visibilityType |
P183599
|
FINISHED |
| Object | sea navigation 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: sea navigation light | Statement: [Ratnagiri Lighthouse, visibilityType, sea navigation light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityType Context triple: [Ratnagiri Lighthouse, visibilityType, sea navigation light]
-
A.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
B.
visibilityControlledBy
Indicates that the visibility or hidden/shown state of one entity is determined or governed by another entity.
-
C.
visibilityReason
Indicates the reason or cause for why something is visible or has become visible in a given context.
-
D.
visibilityRequirement
Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
-
E.
visibilityRole
Indicates the role or level of access an entity has in determining what information or content is visible to others.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.