Triple
T19112724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew 25 |
E467829
|
entity |
| Predicate | audienceInText |
P74744
|
FINISHED |
| Object | Jesus’ disciples |
—
|
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: Jesus’ disciples | Statement: [Matthew 25, audienceInText, Jesus’ disciples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceInText Context triple: [Matthew 25, audienceInText, Jesus’ disciples]
-
A.
audienceWithinStory
Indicates that an audience exists as an internal, in-story observer or listener within the narrative itself, rather than outside it.
-
B.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
C.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
D.
speakerInText
Indicates that a given entity is the person who speaks or is quoted within a particular text or textual segment.
-
E.
audienceMember
chosen
Indicates that one entity is an audience member who is attending, observing, or listening to a performance, event, or presentation involving the other entity.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39553708190b64e24e1d190833e |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.