Triple
T6957280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucknell University |
E161277
|
entity |
| Predicate | historicalBaptistRoots |
P73762
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bucknell University, historicalBaptistRoots, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalBaptistRoots Context triple: [Bucknell University, historicalBaptistRoots, true]
-
A.
ChristianBranch
Indicates that one entity is a branch, denomination, or subgroup within the broader Christian religious tradition of the other entity.
-
B.
hasDioceseHistory
Indicates that an entity has an associated historical record or account of its diocese, including its past developments, changes, or events.
-
C.
establishedChurch
Indicates that a particular church is officially recognized and supported by the state as its formal or primary religious institution.
-
D.
isHistoricDioceseBishop
Indicates that a person holds or held the office of bishop in a diocese recognized as historic.
-
E.
apostolicOrigin
Indicates that something originates from, is derived from, or is directly linked in authority or tradition to the apostles.
- F. None of above. chosen
Provenance (4 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dad0e52081908b524dc6a66bab01 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d9bb57e88190a3a7cec34e3b617f |
completed | March 27, 2026, 7:25 p.m. |
Created at: March 27, 2026, 2:29 p.m.