Triple
T4767840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visitation |
E105854
|
entity |
| Predicate | MaryJourneyDirection |
P27471
|
FINISHED |
| Object | from Nazareth to the hill country of Judea |
—
|
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: from Nazareth to the hill country of Judea | Statement: [Visitation, MaryJourneyDirection, from Nazareth to the hill country of Judea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MaryJourneyDirection Context triple: [Visitation, MaryJourneyDirection, from Nazareth to the hill country of Judea]
-
A.
journeyFrom
chosen
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
B.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
C.
canProvideDirections
Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
-
D.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
E.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.