Triple
T34682141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rector Major |
E890648
|
entity |
| Predicate | historicalFirstHolder |
P153898
|
FINISHED |
| Object | Saint John Bosco |
—
|
NE NERFINISHED |
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: Saint John Bosco | Statement: [Rector Major, historicalFirstHolder, Saint John Bosco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalFirstHolder Context triple: [Rector Major, historicalFirstHolder, Saint John Bosco]
-
A.
first_holder
chosen
Indicates that the subject is the earliest or original holder or possessor of the specified object, title, or right.
-
B.
wasFirstHeldBy
Indicates that an event or activity was initially hosted, organized, or conducted by a particular entity.
-
C.
lastSignificantHolder
Indicates that one entity is the most recent entity to have held or possessed another entity in a meaningful or legally recognized way.
-
D.
firstHoldersBelongedTo
Indicates that the initial holders or owners of something were members of, or affiliated with, a particular group, organization, or category.
-
E.
alsoHeldByFirstHolder
Indicates that something possessed or held by a second holder is (or was) also possessed or held by the first holder.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: May 1, 2026, 2:05 a.m.