Triple
T23861537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathanael |
E592462
|
entity |
| Predicate | hasFeastTraditionWith |
P154228
|
FINISHED |
| Object | Bartholomew |
—
|
NE NERFINISHED |
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: Bartholomew | Statement: [Nathanael, hasFeastTraditionWith, Bartholomew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeastTraditionWith Context triple: [Nathanael, hasFeastTraditionWith, Bartholomew]
-
A.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
B.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
C.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
-
D.
feastTraditionalName
Indicates the traditional or customary name by which a particular feast or celebration is known.
-
E.
feastRelatedTo
Indicates a relationship in which one entity is connected or relevant to a feast, such as by association, participation, context, or thematic linkage.
- F. None of above. chosen
Provenance (4 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae0b4bc819089f491d9e817d160 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:13 p.m.