Triple
T23168077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Scotland |
E578765
|
entity |
| Predicate | hasLocalUnit |
P151190
|
FINISHED |
| Object | parish |
—
|
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: parish | Statement: [Catholic Church in Scotland, hasLocalUnit, parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalUnit Context triple: [Catholic Church in Scotland, hasLocalUnit, parish]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
hasUnitFeature
Indicates that something possesses a specific unit-related characteristic or attribute, such as a measurable feature expressed in defined units.
-
C.
isLocalQuantity
Indicates that a quantity is specific to a particular context, location, or subsystem rather than being globally applicable.
-
D.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
-
E.
hasReachUnit
Indicates that one entity uses a specified unit of measurement to express its reach or extent.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2d51288190af0d5747090d8e5d |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:03 p.m.