Triple
T13436269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saints of the Holy Land (tradition) |
E320236
|
entity |
| Predicate | includesSaintsWho |
P38232
|
FINISHED |
| Object | lived in the Holy Land |
—
|
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: lived in the Holy Land | Statement: [Saints of the Holy Land (tradition), includesSaintsWho, lived in the Holy Land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSaintsWho Context triple: [Saints of the Holy Land (tradition), includesSaintsWho, lived in the Holy Land]
-
A.
includesSaintsFrom
chosen
Indicates that one collection, group, or set contains or incorporates saints that originate from or belong to another specified source or context.
-
B.
saintName
Indicates that an entity has the specified name under which they are recognized or venerated as a saint.
-
C.
numberOfSaints
Indicates the numerical count of saints associated with a given entity or context.
-
D.
linkedToSaint
Indicates that one entity has a direct association or connection with a saint.
-
E.
hasPatronSaint
Indicates that one entity serves as the patron saint associated with, protecting, or representing another 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee42a8c8190a85716b4a6db335e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.