Triple
T19014593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chronicle |
E465313
|
entity |
| Predicate | hasAuthorReligiousStatus |
P27703
|
FINISHED |
| Object | recluse |
—
|
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: recluse | Statement: [The Chronicle, hasAuthorReligiousStatus, recluse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorReligiousStatus Context triple: [The Chronicle, hasAuthorReligiousStatus, recluse]
-
A.
religiousAuthorityStatus
Indicates the role or level of recognized authority an entity holds within a religious or spiritual hierarchy.
-
B.
hasReligiousCharacter
chosen
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
C.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
D.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
E.
hasReligiousRoleEquivalent
Indicates that two religious roles are considered functionally or hierarchically equivalent within or across religious traditions.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6d9f2a081908c0e923809da88e2 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.