Triple
T11126406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Lakers–Los Angeles Clippers rivalry |
E263149
|
entity |
| Predicate | isDerbyMatchup |
P45389
|
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: [Los Angeles Lakers–Los Angeles Clippers rivalry, isDerbyMatchup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerbyMatchup Context triple: [Los Angeles Lakers–Los Angeles Clippers rivalry, isDerbyMatchup, true]
-
A.
isDivisionalMatchup
Indicates that the two entities (typically teams) are competing against each other within the same division.
-
B.
playsInDerbyWith
chosen
Indicates that two entities participate together as opponents or competitors in the same derby event or match.
-
C.
playsInDerby
Indicates participation by an entity as a competitor or performer in a derby event.
-
D.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
-
E.
derbyInLeagueSystem
Indicates that a derby (a match between local rivals) takes place within, and is organized as part of, a specific league system.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7e82fc5f88190b34c55de3d50f6a7 |
completed | April 9, 2026, 5:55 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.