Triple
T38053608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mtarfa |
E949838
|
entity |
| Predicate | parishStatusSince |
P153991
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Mtarfa, parishStatusSince, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishStatusSince Context triple: [Mtarfa, parishStatusSince, 2000]
-
A.
hasParishStatusSince
chosen
Indicates that an entity has held the status of a parish continuously starting from a specified point in time.
-
B.
ecclesiasticalParishStatus
Indicates the formal ecclesiastical status or standing of a parish within a church’s organizational structure.
-
C.
parishEstablished
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
D.
parishStatusBeforeCathedral
Indicates the status or condition of a parish as it existed prior to the establishment or designation of a cathedral.
-
E.
hasAncientParishStatus
Indicates that an entity possesses the legal or historical status of being an ancient parish.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.