Triple
T1440664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League men's basketball |
E31061
|
entity |
| Predicate | homeVenuesType |
P25526
|
FINISHED |
| Object | on-campus arenas |
—
|
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: on-campus arenas | Statement: [Ivy League men's basketball, homeVenuesType, on-campus arenas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenuesType Context triple: [Ivy League men's basketball, homeVenuesType, on-campus arenas]
-
A.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
B.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
C.
homeVenueRegion
Indicates the geographic region in which an entity’s primary or home venue is located.
-
D.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
E.
venueConcept
Indicates a relationship where a venue is associated with, characterized by, or defined in terms of a particular concept or thematic idea.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.