Triple
T33212962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021–22 NBA G League season |
E850208
|
entity |
| Predicate | featuresTwoWayContracts |
P188071
|
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, featuresTwoWayContracts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTwoWayContracts Context triple: [2021–22 NBA G League season, featuresTwoWayContracts, true]
-
A.
usedTwoWayContractRule
Indicates that a two-way contractual rule or agreement was applied reciprocally between the involved parties.
-
B.
twoWayCommunication
Indicates a reciprocal exchange of information between two entities, where each can both send and receive messages from the other.
-
C.
sideTwoIncludes
Indicates that the second side in a relationship or comparison contains, encompasses, or includes the first side.
-
D.
negotiatesBetween
Indicates a relationship where an entity acts as an intermediary to facilitate negotiation or mediation between two other entities.
-
E.
featuresDualRole
chosen
Indicates that an entity simultaneously fulfills two distinct roles or functions within a given context.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a017a360f088190acd5933aa353e763 |
completed | May 11, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_6a0179d3f78c8190b1d2e8829619fa54 |
completed | May 11, 2026, 6:40 a.m. |
Created at: May 1, 2026, 1:30 a.m.