Triple
T27511421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Fitton |
E694425
|
entity |
| Predicate | hasPlaceOfHonor |
P177518
|
FINISHED |
| Object | College of the Holy Cross |
—
|
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: College of the Holy Cross | Statement: [James Fitton, hasPlaceOfHonor, College of the Holy Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceOfHonor Context triple: [James Fitton, hasPlaceOfHonor, College of the Holy Cross]
-
A.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
B.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
-
C.
hasCodeOfHonor
Indicates that an entity adheres to a personal or shared ethical code that guides its behavior and decisions.
-
D.
namedInHonorBy
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
E.
hallOfFameOrRecognition
Indicates a relationship where an entity has been formally honored, inducted, or recognized in a hall of fame or comparable recognition context.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 27, 2026, 1:16 p.m.