Triple
T3065539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Catherine's Lighthouse |
E62095
|
entity |
| Predicate | originallyBuilt |
P44202
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [St Catherine's Lighthouse, originallyBuilt, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyBuilt Context triple: [St Catherine's Lighthouse, originallyBuilt, 19th century]
-
A.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
B.
wasOriginallyBuiltAs
Indicates that an object or structure was initially constructed for a particular purpose, function, or role, which may differ from its current use.
-
C.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
D.
originallyHad
Indicates that an entity previously possessed, contained, or was associated with something before a change, loss, or transformation occurred.
-
E.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0fc01dc81908fbdf7c1ef73afe4 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f7630c81908e1ca8a69611cff6 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.