Triple
T29926681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Philip |
E760098
|
entity |
| Predicate | askedQuestionToJesusAbout |
P168270
|
FINISHED |
| Object | feeding the five thousand |
—
|
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: feeding the five thousand | Statement: [Saint Philip, askedQuestionToJesusAbout, feeding the five thousand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: askedQuestionToJesusAbout Context triple: [Saint Philip, askedQuestionToJesusAbout, feeding the five thousand]
-
A.
guidingQuestionOf
Indicates that one item serves as a guiding or central question that frames, directs, or structures another item (such as a discussion, activity, or work).
-
B.
questionConveyedBy
Indicates that a particular question is expressed, communicated, or represented by a given medium, message, or artifact.
-
C.
questionText
Indicates the textual content of a question as it is posed or displayed.
-
D.
typicalQuestion
Indicates that an entity is a common or standard question typically asked in a given context or situation.
-
E.
questionAsksWhether
Indicates that one entity poses a question to determine if a particular condition, fact, or proposition is true or not.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67797fe5c81909575b762f32b63ef |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:16 p.m.