Triple
T28118500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portmoak parish |
E710708
|
entity |
| Predicate | hasLongStanding |
P71432
|
FINISHED |
| Object | local church history |
—
|
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: local church history | Statement: [Portmoak parish, hasLongStanding, local church history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongStanding Context triple: [Portmoak parish, hasLongStanding, local church history]
-
A.
isLongStanding
Indicates that a relationship, condition, or state has existed for a considerable or extended period of time.
-
B.
hasLongHistory
chosen
Indicates that the relationship or subject has existed or persisted over a long period of time.
-
C.
hasPermanentSeniority
Indicates that one entity holds a fixed, enduring precedence or higher rank over another that does not change over time.
-
D.
hasSeniorityStatus
Indicates that one entity holds a particular level or classification of seniority relative to others.
-
E.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 9:15 p.m.