Triple
T4783992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Examen |
E106431
|
entity |
| Predicate | isReadBy |
P18381
|
FINISHED |
| Object | Jesuit candidates |
—
|
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: Jesuit candidates | Statement: [General Examen, isReadBy, Jesuit candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReadBy Context triple: [General Examen, isReadBy, Jesuit candidates]
-
A.
hasReading
Indicates that an entity is associated with a particular reading, such as a measured value, interpretation, or recorded observation.
-
B.
readBy
chosen
Indicates that a particular text, document, or content item has been read or consumed by a specific person or agent.
-
C.
alsoReadBy
Indicates that an item (such as a document, article, or book) has been read by another user or entity in addition to the primary one under consideration.
-
D.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
-
E.
isFreeToRead
Indicates that access to the referenced content or resource does not require payment and can be read without cost.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.