Triple
T27076829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head Harbour (East Quoddy) Lighthouse |
E685484
|
entity |
| Predicate | hasAutomationDate |
P45959
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Head Harbour (East Quoddy) Lighthouse, hasAutomationDate, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutomationDate Context triple: [Head Harbour (East Quoddy) Lighthouse, hasAutomationDate, 20th century]
-
A.
automationDate
chosen
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
-
B.
automatedBy
Indicates that an action, process, or function is carried out or controlled by an automated system or mechanism.
-
C.
automatedIn
Indicates that an action, process, or operation is performed automatically within or by a specified system, context, or environment.
-
D.
canAutomate
Indicates that one entity has the capability to perform, control, or execute another entity’s process or task automatically without continuous human intervention.
-
E.
yearOfAutomation
Indicates the specific year in which an entity or process became automated.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:31 a.m.