Triple
T31915112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Towson Tigers men's lacrosse |
E814805
|
entity |
| Predicate | notableRivalryRegion |
P80695
|
FINISHED |
| Object | Maryland |
E707
|
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: Maryland | Statement: [Towson Tigers men's lacrosse, notableRivalryRegion, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRivalryRegion Context triple: [Towson Tigers men's lacrosse, notableRivalryRegion, Maryland]
-
A.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
B.
rivalryRegion
chosen
Indicates a competitive or adversarial relationship that exists between entities within a specific geographic or regional context.
-
C.
countryOfRivalry
Indicates that one entity is a country with which another entity has a relationship of rivalry or adversarial competition.
-
D.
notableRivalryType
Indicates a specific kind or category of rivalry that characterizes the notable competitive relationship between entities.
-
E.
nicknameOfRivalryBetween
Indicates that one entity is a nickname or informal title used to refer to a particular rivalry between other entities.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb136e510819098db7d0e36be0915 |
completed | June 14, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:02 a.m.