Triple
T19888548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemaquid Point Lighthouse |
E477966
|
entity |
| Predicate | featuredOnYear |
P85580
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Pemaquid Point Lighthouse, featuredOnYear, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredOnYear Context triple: [Pemaquid Point Lighthouse, featuredOnYear, 2003]
-
A.
featuredInYear
chosen
Indicates that something was prominently presented, highlighted, or showcased during a specific calendar year.
-
B.
featuredOn
Indicates that one entity is prominently presented, highlighted, or showcased on or within another entity (such as a platform, publication, or product).
-
C.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
D.
foundInYear
Indicates the specific calendar year in which something was discovered, created, established, or otherwise found.
-
E.
promotionYear
Indicates the year in which an entity was promoted to a new position, rank, or status.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590c1b9c8190abbfaa04b80713b3 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.