Triple
T23970665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Deer |
E604219
|
entity |
| Predicate | hasParishOrigin |
P91038
|
FINISHED |
| Object | New Deer parish |
—
|
NE NERFINISHED |
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: New Deer parish | Statement: [New Deer, hasParishOrigin, New Deer parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishOrigin Context triple: [New Deer, hasParishOrigin, New Deer parish]
-
A.
hasTraditionalParish
chosen
Indicates that an entity is associated with or belongs to a specific traditional parish.
-
B.
hasParishHistory
Indicates that an entity possesses or is associated with a documented historical record of a parish.
-
C.
hasApostolicOriginFrom
Indicates that something (typically a doctrine, tradition, or authority) originates from, or is derived through, the apostles or their foundational teaching.
-
D.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
E.
usesParishSystem
Indicates that an entity organizes its local governance, administration, or jurisdiction according to a parish-based system.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dc3f088190a55faf6f01ddf4bf |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.