Triple
T33123488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomasian |
E847661
|
entity |
| Predicate | associatedWithInstitutionNickname |
P29026
|
FINISHED |
| Object | UST |
E238150
|
NE 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: UST | Statement: [Thomasian, associatedWithInstitutionNickname, UST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithInstitutionNickname Context triple: [Thomasian, associatedWithInstitutionNickname, UST]
-
A.
associatedInstitutionNickname
chosen
Indicates that an institution is commonly known or referred to by a particular nickname.
-
B.
associatedWithCurrentInstitutionName
Indicates that an entity has an affiliation or connection with the institution identified by the current institution name.
-
C.
associatedWithInstitution
Indicates that an entity has a formal or recognized connection or affiliation with an institution.
-
D.
associatedInstitution
Indicates that an entity has a formal connection or affiliation with a particular institution.
-
E.
associatedInstitutionType
Indicates the type or category of institution with which an entity is associated.
- F. None of above.
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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35161646c481909c233544ee056e50 |
completed | June 19, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.