Triple
T4851079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistle of Barnabas |
E108413
|
entity |
| Predicate | statusInAlexandria |
P55453
|
FINISHED |
| Object | highly esteemed |
—
|
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: highly esteemed | Statement: [Epistle of Barnabas, statusInAlexandria, highly esteemed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInAlexandria Context triple: [Epistle of Barnabas, statusInAlexandria, highly esteemed]
-
A.
statusInLateAntiquity
Indicates the social, political, or cultural standing that an entity held during the historical period of Late Antiquity.
-
B.
officeEndAsPatriarchOfAlexandria
Indicates the time or event at which a person’s tenure as Patriarch of Alexandria comes to an end.
-
C.
AlexandriaTitle
chosen
Indicates that an entity holds a specific title, role, or designation associated with Alexandria.
-
D.
officeStartAsPatriarchOfAlexandria
Indicates the time or event at which an individual begins their tenure serving as the Patriarch of Alexandria.
-
E.
statusInEgypt
Indicates the legal, social, or official condition or standing that an entity holds specifically within the context of Egypt.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.