Triple
T31269190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Cana |
E797335
|
entity |
| Predicate | hasAllegedLocationOf |
P182277
|
FINISHED |
| Object | stone jars of Cana tradition |
—
|
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: stone jars of Cana tradition | Statement: [Sanctuary of Cana, hasAllegedLocationOf, stone jars of Cana tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllegedLocationOf Context triple: [Sanctuary of Cana, hasAllegedLocationOf, stone jars of Cana tradition]
-
A.
allegedSupportLocation
Indicates a claimed or reported place where support (such as assistance, resources, or backing) is said to have been provided or received.
-
B.
allegedMisconductLocation
chosen
Indicates the place where the alleged misconduct is reported to have occurred.
-
C.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 29, 2026, 9:13 p.m.