Triple
T2283207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Mark |
E51325
|
entity |
| Predicate | traditionHoldsThat |
P13958
|
FINISHED |
| Object | First bishop of Alexandria |
—
|
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: First bishop of Alexandria | Statement: [John Mark, traditionHoldsThat, First bishop of Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionHoldsThat Context triple: [John Mark, traditionHoldsThat, First bishop of Alexandria]
-
A.
traditionAscribes
chosen
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
B.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
C.
traditionsMaintainedBy
Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
-
D.
governedWithinTradition
Indicates that an entity’s actions, decisions, or organization are regulated or constrained according to a particular established tradition or customary framework.
-
E.
traditionIncludes
Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21d6d748190980128c1bc5b9621 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.