Triple
T13926378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleopas |
E334870
|
entity |
| Predicate | companionOnJourney |
P22642
|
FINISHED |
| Object | unnamed disciple |
—
|
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: unnamed disciple | Statement: [Cleopas, companionOnJourney, unnamed disciple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionOnJourney Context triple: [Cleopas, companionOnJourney, unnamed disciple]
-
A.
companionOf
chosen
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
companionsCategory
Indicates that one entity is classified under a specific category related to companions or companionship.
-
C.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
D.
hasNumberOfCompanions
Indicates the quantity of companions or associates that an entity has.
-
E.
viewOnCompanions
Indicates a relationship where one entity holds a particular opinion, perspective, or attitude about its companions or associated entities.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa7e9248190b0523415b9224e2f |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.