Triple
T4257655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saybrook College |
E96017
|
entity |
| Predicate | hasMasterTitleHistorical |
P23724
|
FINISHED |
| Object | Master |
—
|
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: Master | Statement: [Saybrook College, hasMasterTitleHistorical, Master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMasterTitleHistorical Context triple: [Saybrook College, hasMasterTitleHistorical, Master]
-
A.
hasMasterTitleFormer
chosen
Indicates that an entity previously held, but no longer holds, a particular master title.
-
B.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
-
D.
hasMajorTitle
Indicates that an entity holds or has been awarded a significant, high-prestige title or championship.
-
E.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ec321008190b2cc1aca6ab690c4 |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.