Triple
T30390966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue–Green Rivalry |
E773082
|
entity |
| Predicate | isAlsoContestedIn |
P28246
|
FINISHED |
| Object | other NCAA sports |
—
|
LITERAL 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: other NCAA sports | Statement: [Blue–Green Rivalry, isAlsoContestedIn, other NCAA sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlsoContestedIn Context triple: [Blue–Green Rivalry, isAlsoContestedIn, other NCAA sports]
-
A.
alsoContestedIn
chosen
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
B.
areContestedIn
Indicates that something is the subject of dispute, challenge, or competition within a particular context, event, or process.
-
C.
wasContestedIn
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
D.
laterContestedBy
Indicates that an earlier claim, decision, or statement is subsequently challenged or disputed by another party or source.
-
E.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6859bbd7c81909084682a99f2b9be |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.