Triple
T32076865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leones de Ponce |
E819178
|
entity |
| Predicate | hasHostedHomeGamesSince |
P30599
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [Leones de Ponce, hasHostedHomeGamesSince, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostedHomeGamesSince Context triple: [Leones de Ponce, hasHostedHomeGamesSince, 1940s]
-
A.
homeFieldSince
Indicates that a particular location has served as the designated home field or home venue for an entity starting from a specified point in time.
-
B.
playedHomeGamesFrom
chosen
Indicates the time period during which a team or player hosted their home games at a particular venue.
-
C.
playedHomeGamesUntil
Indicates the period up to which a team or player hosted their home games at a particular venue.
-
D.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
-
E.
playsHomeGamesFor
Indicates that a sports team or player hosts their home games on behalf of, or as a representative of, a particular organization, club, or location.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 12:23 a.m.