Triple
T2143646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephrem the Syrian |
E47014
|
entity |
| Predicate | clericalStatus |
P18869
|
FINISHED |
| Object | deacon |
—
|
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: deacon | Statement: [Ephrem the Syrian, clericalStatus, deacon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clericalStatus Context triple: [Ephrem the Syrian, clericalStatus, deacon]
-
A.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
B.
hasFormalStatus
chosen
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
C.
careerStatus
Indicates the current stage, position, or condition of an entity within its professional or occupational life.
-
D.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
-
E.
statutoryType
Indicates the specific legal or statutory category under which something is formally classified or regulated.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.