Triple
T6004244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Central–North Carolina A&T rivalry |
E133668
|
entity |
| Predicate | isHBCURivalry |
P68656
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [North Carolina Central–North Carolina A&T rivalry, isHBCURivalry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHBCURivalry Context triple: [North Carolina Central–North Carolina A&T rivalry, isHBCURivalry, true]
-
A.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
B.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
C.
hasForeignRival
Indicates that an entity has at least one rival that is based in or originates from a different country or foreign jurisdiction.
-
D.
hasRivalrySeries
Indicates a recurring competitive relationship or series of contests held between two entities.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- F. None of above. chosen
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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f10d18081908c351170b7f58d3d |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:06 p.m.