Triple
T24766550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Basketball Association |
E619598
|
entity |
| Predicate | importsAllowedIn |
P158723
|
FINISHED |
| Object | Governors’ Cup |
—
|
NE NERFINISHED |
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: Governors’ Cup | Statement: [Philippine Basketball Association, importsAllowedIn, Governors’ Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importsAllowedIn Context triple: [Philippine Basketball Association, importsAllowedIn, Governors’ Cup]
-
A.
allowsImports
chosen
Indicates that one entity permits another entity to bring in or receive items, data, or resources from an external source.
-
B.
isStillAllowedFor
Indicates that one entity continues to have permission or authorization to access, use, or perform something in relation to another entity.
-
C.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
-
D.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
E.
collectingAllowed
Indicates whether an entity is permitted to collect or gather specified items, data, or resources.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 4:28 a.m.