Triple
T5155873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flat Holm Lighthouse |
E116306
|
entity |
| Predicate | automatedIn |
P62270
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Flat Holm Lighthouse, automatedIn, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: automatedIn Context triple: [Flat Holm Lighthouse, automatedIn, 1988]
-
A.
canAutomate
Indicates that one entity has the capability to perform, control, or execute another entity’s process or task automatically without continuous human intervention.
-
B.
autonomousFor
Indicates that one entity operates or makes decisions independently on behalf of, or in place of, another specified context, system, or agent.
-
C.
isRobotic
Indicates that an entity is robotic, meaning it is a robot or operates using robotic mechanisms or technology.
-
D.
automaticallyHeld
Indicates that the holding or possession relationship occurs by default or system rule, without requiring an explicit action or decision by the involved entities.
-
E.
isArtificial
Indicates that an entity is man-made or produced by human design rather than occurring naturally.
- F. None of above. chosen
Provenance (4 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79bf9b088190a556dc02f10204e4 |
completed | March 20, 2026, 4:45 p.m. |
Created at: March 20, 2026, 1:44 p.m.