Triple
T4365217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Poge Lighthouse |
E98754
|
entity |
| Predicate | firstLightingDate |
P18472
|
FINISHED |
| Object | 1801 |
—
|
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: 1801 | Statement: [Cape Poge Lighthouse, firstLightingDate, 1801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLightingDate Context triple: [Cape Poge Lighthouse, firstLightingDate, 1801]
-
A.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
B.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
C.
firstProducedAt
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first time.
-
D.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
E.
firstAppearedAt
chosen
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351fea3e88190807b99868982c491 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.