Triple
T2493000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCLA Bruins men’s basketball |
E52087
|
entity |
| Predicate | historicEraOfDominance |
P5898
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [UCLA Bruins men’s basketball, historicEraOfDominance, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicEraOfDominance Context triple: [UCLA Bruins men’s basketball, historicEraOfDominance, 1960s]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
C.
timePeriodOfDominance
chosen
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
D.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
-
E.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd192cad08190b13bf8e2d7149199 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.