Triple
T17745422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinghorn parish |
E442973
|
entity |
| Predicate | hasHistoricRecordType |
P2554
|
FINISHED |
| Object | Old Parish Registers |
—
|
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: Old Parish Registers | Statement: [Kinghorn parish, hasHistoricRecordType, Old Parish Registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricRecordType Context triple: [Kinghorn parish, hasHistoricRecordType, Old Parish Registers]
-
A.
hasHistoricResourceType
Indicates that an entity is associated with a particular category or type of historic resource.
-
B.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
hasHistoricProperty
Indicates that one entity possesses, contains, or is associated with a property that has historical significance or heritage value.
-
D.
hasRecordType
chosen
Indicates that an entity is associated with or classified under a specific type or category of record.
-
E.
hasHistoricMP
Indicates that an entity is or has been represented by a specific Member of Parliament at some point in the past.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ad0c5b481909059bfa868cc4001 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.