Triple
T30673239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Thing |
E780847
|
entity |
| Predicate | teamRivalry |
P74502
|
FINISHED |
| Object | Yancy Street Gang |
—
|
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: Yancy Street Gang | Statement: [The Thing, teamRivalry, Yancy Street Gang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRivalry Context triple: [The Thing, teamRivalry, Yancy Street Gang]
-
A.
associatedRivalry
chosen
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
B.
conferenceRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
-
C.
divisionRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
-
D.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
E.
hasRivalryEmotion
Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b159e3881908e7d125ae27eab41 |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:32 p.m.