Triple
T30701610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thangassery Lighthouse |
E781624
|
entity |
| Predicate | towerMarking |
P29692
|
FINISHED |
| Object | white and red bands |
—
|
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: white and red bands | Statement: [Thangassery Lighthouse, towerMarking, white and red bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerMarking Context triple: [Thangassery Lighthouse, towerMarking, white and red bands]
-
A.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
-
B.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
C.
tower
Indicates that one entity is a tall, prominent structure rising above its surroundings, often used for observation, support, or communication.
-
D.
towerColor
chosen
Indicates the color attribute associated with a tower in the relationship.
-
E.
towerAttachment
Indicates that one entity is physically attached to or structurally connected with a tower.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68bdf2b3c81909578a19e0190e45d |
completed | May 2, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:34 p.m.