Triple
T167497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Chop Light |
E3047
|
entity |
| Predicate | marking |
P401
|
FINISHED |
| Object | white cylindrical tower |
—
|
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 cylindrical tower | Statement: [West Chop Light, marking, white cylindrical tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marking Context triple: [West Chop Light, marking, white cylindrical tower]
-
A.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
B.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
C.
flag
chosen
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
D.
mentions
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
E.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25884c8d88190bc4cb4e3541e8116 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25665f5b8819096ca3e084faf976e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.