Triple
T248406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA rules |
E5086
|
entity |
| Predicate | require |
P100
|
FINISHED |
| Object | team to have five players on court unless disqualified |
—
|
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 to have five players on court unless disqualified | Statement: [NBA rules, require, team to have five players on court unless disqualified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: require Context triple: [NBA rules, require, team to have five players on court unless disqualified]
-
A.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
C.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
D.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
E.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.