Triple
T3602508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston University |
E76289
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BU |
E76289
|
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: BU | Statement: [Boston University, abbreviation, BU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BU Context triple: [Boston University, abbreviation, BU]
-
A.
BU
chosen
BU is a major private research university in Boston, Massachusetts, known for its diverse academic programs and global student body.
-
B.
BU
BU is a historic vehicle registration prefix that was once used to identify motor vehicles registered in Buckinghamshire, England.
-
C.
BUR
BUR is the three-letter IATA airport code for Hollywood Burbank Airport, a commercial airport serving the Los Angeles area in Southern California.
-
D.
BAL
BAL is the Amtrak station code for Pennsylvania Station in Baltimore, Maryland, a major rail hub in the city’s transportation network.
-
E.
BO
BO is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Bolivia in international standards and systems.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1dd264c819098796f5f50f251be |
completed | March 8, 2026, 6:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4031dce448190b112ba4d5fa16ee0 |
completed | March 13, 2026, 12:29 p.m. |
Created at: March 8, 2026, 3:22 p.m.