Triple
T12246799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCLA Bruins softball |
E291870
|
entity |
| Predicate | isPowerhouseProgram |
P12148
|
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: [UCLA Bruins softball, isPowerhouseProgram, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPowerhouseProgram Context triple: [UCLA Bruins softball, isPowerhouseProgram, true]
-
A.
checksPowerOf
Indicates that one entity verifies or determines whether another entity possesses a specified level or amount of power.
-
B.
isPowerConference
Indicates that an athletic conference is considered a major or elite "power" conference within its sport or league.
-
C.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
D.
hasStrongProgramIn
chosen
Indicates that an institution or organization offers a particularly high-quality or well-regarded program in a specified field or area.
-
E.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.