Triple
T23950136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Celtics vs Detroit Pistons |
E603022
|
entity |
| Predicate | typicalGamePace |
P154466
|
FINISHED |
| Object | slow, half-court oriented |
—
|
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: slow, half-court oriented | Statement: [Boston Celtics vs Detroit Pistons, typicalGamePace, slow, half-court oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGamePace Context triple: [Boston Celtics vs Detroit Pistons, typicalGamePace, slow, half-court oriented]
-
A.
typicalGameTime
Indicates the usual or expected amount of time a game takes to play.
-
B.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
C.
isFastPaced
Indicates that an activity, event, or process proceeds quickly with rapid progression and little downtime.
-
D.
typicalPlayTime
Indicates the usual or average amount of time an entity is expected to be played or used in a play session.
-
E.
typicalPlayTimeMinutes
Indicates the usual or average number of minutes an activity, game, or media item is typically played or experienced.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d03140f08190b4356626628ff56f |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:19 p.m.