Triple
T10629573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hegesippus |
E250415
|
entity |
| Predicate | testifiedTo |
P18400
|
FINISHED |
| Object | unity of faith in early churches |
—
|
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: unity of faith in early churches | Statement: [Hegesippus, testifiedTo, unity of faith in early churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testifiedTo Context triple: [Hegesippus, testifiedTo, unity of faith in early churches]
-
A.
gaveTestimonyIn
Indicates that one entity provided formal testimony or a statement in an official proceeding, event, or context associated with another entity.
-
B.
hasTestimony
Indicates that an entity provides, contains, or is associated with a formal statement or account (testimony) about another entity or event.
-
C.
attestedBy
chosen
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
-
D.
testimonyAffects
Indicates that one party’s testimony has an influence or impact on another entity, situation, or outcome.
-
E.
attestedAs
Indicates that something is documented, recorded, or certified as having a particular status, form, or property.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df92f8388190a8bcff96809d8eb4 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9 p.m.