Triple
T2564121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian saints |
E57309
|
entity |
| Predicate | hasSourceOfInformation |
P26860
|
FINISHED |
| Object | hagiographies |
—
|
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: hagiographies | Statement: [Christian saints, hasSourceOfInformation, hagiographies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceOfInformation Context triple: [Christian saints, hasSourceOfInformation, hagiographies]
-
A.
usesInformationSources
chosen
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
B.
requiresSourceDisclosure
Indicates that performing or using something is contingent on revealing or making known the origin or source from which it was derived.
-
C.
hasSecondarySource
Indicates that an entity is supported, documented, or referenced by a secondary source rather than by a primary or original source.
-
D.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
E.
attestedFrom
Indicates the earliest point in time or source from which something is documented, recorded, or evidenced as existing or in use.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.