Triple
T13418741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naparima College |
E313282
|
entity |
| Predicate | hasReligiousRoots |
P22741
|
FINISHED |
| Object | historic Presbyterian roots |
—
|
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: historic Presbyterian roots | Statement: [Naparima College, hasReligiousRoots, historic Presbyterian roots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousRoots Context triple: [Naparima College, hasReligiousRoots, historic Presbyterian roots]
-
A.
hasReligiousOrigin
chosen
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
-
B.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
C.
hasEponymReligion
Indicates that a religion is named after or derived from the name of a particular person.
-
D.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
E.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb8416c8190a00dde0917c26f51 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:39 p.m.