Triple
T29990972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Gold Miners |
E761877
|
entity |
| Predicate | homeUniversityCampus |
P269
|
FINISHED |
| Object | California State University, Sacramento |
—
|
NE NERFINISHED |
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: California State University, Sacramento | Statement: [Sacramento Gold Miners, homeUniversityCampus, California State University, Sacramento]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeUniversityCampus Context triple: [Sacramento Gold Miners, homeUniversityCampus, California State University, Sacramento]
-
A.
publicUniversityCampus
Indicates that a university campus is publicly funded or state-operated rather than privately owned.
-
B.
campus
chosen
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
C.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
-
D.
cityCampus
Indicates that a campus is located within or associated with a particular city.
-
E.
campus2
Indicates that one entity is a secondary or additional campus location associated with another primary campus or institution.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791aa82c8190afb7c808cddbf46a |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:38 p.m.