Triple
T3744250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA game |
E79772
|
entity |
| Predicate | tieAllowedAfterRegulation |
P51223
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [NBA game, tieAllowedAfterRegulation, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieAllowedAfterRegulation Context triple: [NBA game, tieAllowedAfterRegulation, no]
-
A.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
B.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
-
C.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
D.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
E.
mayRuleOver
Indicates that one entity has the potential or permission to exercise authority or governance over another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.