Triple
T35562297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference (NBA G League) |
E1027667
|
entity |
| Predicate | isGeographicallyBased |
P115992
|
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: [Western Conference (NBA G League), isGeographicallyBased, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeographicallyBased Context triple: [Western Conference (NBA G League), isGeographicallyBased, true]
-
A.
isGeographicallySpecific
Indicates that something is limited to or uniquely associated with a particular geographic location or area.
-
B.
hasGeographicBasis
chosen
Indicates that something is grounded in, derived from, or defined by a particular geographic location or area.
-
C.
hasTypicalGeographicOrigin
Indicates that an entity is commonly or characteristically associated with originating from a particular geographic location.
-
D.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
E.
isGeographicCode
Indicates that one entity functions as a geographic code that identifies or represents the location of 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.