Triple
T3744266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA game |
E79772
|
entity |
| Predicate | timeoutType |
P14162
|
FINISHED |
| Object | team timeouts |
—
|
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: team timeouts | Statement: [NBA game, timeoutType, team timeouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeoutType Context triple: [NBA game, timeoutType, team timeouts]
-
A.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
timeType
chosen
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
C.
timeAfterAble
Indicates that one event, state, or action occurs after another point in time at which it becomes possible or permissible.
-
D.
terminationCondition
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
-
E.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb58c9048190a055d1f4a7e6b699 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.