Triple
T6485022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladd–Peebles Stadium |
E146485
|
entity |
| Predicate | tenantPeriod |
P46529
|
FINISHED |
| Object | South Alabama Jaguars football 2009–2019 |
—
|
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: South Alabama Jaguars football 2009–2019 | Statement: [Ladd–Peebles Stadium, tenantPeriod, South Alabama Jaguars football 2009–2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantPeriod Context triple: [Ladd–Peebles Stadium, tenantPeriod, South Alabama Jaguars football 2009–2019]
-
A.
leasePeriod
chosen
Indicates the duration or time span for which a lease agreement is valid between parties.
-
B.
ownershipPeriod
Indicates the span of time during which an entity holds ownership rights over another entity.
-
C.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
D.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
E.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a6efe1881909a044b1cdaa511af |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.