Triple
T30406018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA men's basketball national championship (with Maryland, 2002) |
E773479
|
entity |
| Predicate | MarylandNickname |
P10087
|
FINISHED |
| Object | Terrapins |
—
|
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: Terrapins | Statement: [NCAA men's basketball national championship (with Maryland, 2002), MarylandNickname, Terrapins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MarylandNickname Context triple: [NCAA men's basketball national championship (with Maryland, 2002), MarylandNickname, Terrapins]
-
A.
marylandScore
Indicates the score achieved by a Maryland team or entity in a particular game, event, or evaluation.
-
B.
regionalNickname
Indicates that one entity is an informal or colloquial name used for another entity within a specific geographic region.
-
C.
marylandConference
Indicates that an entity is associated with a conference or athletic conference related to the state of Maryland.
-
D.
stateNickname
chosen
Indicates that one entity is the commonly used nickname or informal moniker for a given state.
-
E.
metropolitanAreaNickname
Indicates that a metropolitan area is known by a particular informal or colloquial nickname.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:03 p.m.