Triple
T26386027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina–NC State football rivalry |
E663281
|
entity |
| Predicate | stateRivalryOf |
P172365
|
FINISHED |
| Object | North Carolina |
—
|
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: North Carolina | Statement: [North Carolina–NC State football rivalry, stateRivalryOf, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRivalryOf Context triple: [North Carolina–NC State football rivalry, stateRivalryOf, North Carolina]
-
A.
countryOfRivalry
Indicates that one entity is a country with which another entity has a relationship of rivalry or adversarial competition.
-
B.
nicknameOfRivalryBetween
Indicates that one entity is a nickname or informal title used to refer to a particular rivalry between other entities.
-
C.
hasRivalState
chosen
Indicates that one state maintains a rivalry or competitive opposition with another state.
-
D.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
E.
conferenceRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 26, 2026, 11:22 p.m.