Triple
T5987302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powers Field at Princeton Stadium |
E133258
|
entity |
| Predicate | campusVenueType |
P25397
|
FINISHED |
| Object | primary football venue |
—
|
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: primary football venue | Statement: [Powers Field at Princeton Stadium, campusVenueType, primary football venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusVenueType Context triple: [Powers Field at Princeton Stadium, campusVenueType, primary football venue]
-
A.
campusFacilityType
chosen
Indicates the specific kind of facility a campus location is classified as (e.g., library, laboratory, residence hall).
-
B.
campusAreaType
Indicates the classification of a campus area according to its type or functional category.
-
C.
campusFacility
Indicates that one entity is a facility that is located on or belongs to a particular campus.
-
D.
campusType
Indicates the classification or category of a campus based on its type (e.g., main, satellite, urban, rural).
-
E.
campusDesignation
Indicates the formal classification or status assigned to a particular campus within an institution or system.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc38a308190a368c5c787a5fc64 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.