Triple
T33212985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021–22 NBA G League season |
E850208
|
entity |
| Predicate | usedTwoWayContractRule |
P180571
|
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: [2021–22 NBA G League season, usedTwoWayContractRule, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTwoWayContractRule Context triple: [2021–22 NBA G League season, usedTwoWayContractRule, true]
-
A.
isContractedBy
Indicates that an entity (such as a service, work, or obligation) is formally engaged or commissioned through a contract by another entity.
-
B.
mayContractWith
Indicates that one entity is permitted or authorized to enter into a contractual agreement with another entity.
-
C.
managedUnderContractWith
Indicates that one entity is responsible for managing another entity or service based on the terms of a formal contract with a specified party.
-
D.
ruleOfTwoFormulatedBy
Indicates that an individual is the originator or creator of the "Rule of Two" principle or doctrine.
-
E.
bilateralRole
Indicates a relationship where each of two entities holds a defined role with respect to the other in a mutual or two-sided interaction.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: May 1, 2026, 1:30 a.m.