Triple
T10699089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Mavericks–Houston Rockets rivalry |
E252221
|
entity |
| Predicate | fanIntensity |
P59318
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Dallas Mavericks–Houston Rockets rivalry, fanIntensity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanIntensity Context triple: [Dallas Mavericks–Houston Rockets rivalry, fanIntensity, high]
-
A.
eraOfIncreasedIntensity
Indicates a period during which the level or strength of a particular activity, condition, or phenomenon becomes significantly higher than before.
-
B.
fanInterestLevel
chosen
Indicates the degree or intensity of enthusiasm or interest that a fan has toward a particular subject, such as a person, team, or work.
-
C.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
-
D.
fanType
Indicates the specific category or kind of fan associated with an entity, such as its design, purpose, or operating principle.
-
E.
fanAge
Indicates that one entity is a fan of another and specifies the fan’s age.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8abd7c81909c274aa1699a3695 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.