Triple
T1112027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Basketball League (NBL) |
E11015
|
entity |
| Predicate | originType |
P4682
|
FINISHED |
| Object | industrial-sponsored league |
—
|
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: industrial-sponsored league | Statement: [National Basketball League (NBL), originType, industrial-sponsored league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originType Context triple: [National Basketball League (NBL), originType, industrial-sponsored league]
-
A.
originalType
chosen
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
B.
originAuthor
Indicates that an entity is the original creator or author of another entity (such as a work, document, or idea).
-
C.
originContext
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
D.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
E.
originNote
Indicates a note or comment that explains the origin, source, or provenance of an entity or relationship.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.