Triple
T183600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States men's national basketball team |
E3930
|
entity |
| Predicate | dominantEra |
P561
|
FINISHED |
| Object | post-1992 professional era |
—
|
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: post-1992 professional era | Statement: [United States men's national basketball team, dominantEra, post-1992 professional era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantEra Context triple: [United States men's national basketball team, dominantEra, post-1992 professional era]
-
A.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
-
B.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
C.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
E.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25926be9c8190a4cfce66f57589d1 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566dfc388190988b1b42d5daaafe |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.