Triple
T30270888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinnaird Head Lighthouse |
E769790
|
entity |
| Predicate | originalStructureUse |
P35487
|
FINISHED |
| Object | castle |
—
|
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: castle | Statement: [Kinnaird Head Lighthouse, originalStructureUse, castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalStructureUse Context triple: [Kinnaird Head Lighthouse, originalStructureUse, castle]
-
A.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
B.
convertedStructureUse
Indicates that an entity’s original structural use has been changed to a different use or function.
-
C.
originalStructureType
chosen
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
D.
originalStructureStatus
Indicates the condition or state of an entity’s initial or pre-modified structure relative to its later or current form.
-
E.
reusesStructureOf
Indicates that one entity adopts or incorporates the structural design or organization of another entity.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: April 29, 2026, 7:43 p.m.