Triple
T7035310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Vermont |
E163366
|
entity |
| Predicate | otherName |
P39
|
FINISHED |
| Object | UVM |
E637212
|
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: UVM | Statement: [University of Vermont, otherName, UVM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UVM Context triple: [University of Vermont, otherName, UVM]
-
A.
UVM
chosen
UVM is a public research university in Burlington, Vermont, known for its strong programs in environmental studies, agriculture, and the liberal arts.
-
B.
UCT
UCT is a leading public research university in Cape Town, South Africa, renowned as one of Africa’s top higher education institutions.
-
C.
Uni
Uni is an Etruscan goddess, broadly equivalent to the Roman Juno and Greek Hera, associated with marriage, fertility, and protection of the state.
-
D.
UVA
UVA is the three-letter IATA airport code assigned to Garner Field Airport in Uvalde, Texas.
-
E.
UVA
UVA is the University of Virginia, a major public research university in Charlottesville known for its strong academics and NCAA Division I athletic programs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e212e28c8190bf38ce9a25d2032e |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c78863c2fc8190b9b54613968742e1 |
completed | March 28, 2026, 7:50 a.m. |
Created at: March 27, 2026, 2:36 p.m.