Triple
T27248133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana Tech Bulldogs baseball |
E687406
|
entity |
| Predicate | homeFacilityComplex |
P101666
|
FINISHED |
| Object | Pat Patterson Park |
—
|
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: Pat Patterson Park | Statement: [Louisiana Tech Bulldogs baseball, homeFacilityComplex, Pat Patterson Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFacilityComplex Context triple: [Louisiana Tech Bulldogs baseball, homeFacilityComplex, Pat Patterson Park]
-
A.
housesFacility
Indicates that one entity serves as a location or container in which the other entity (a facility) is situated or operates.
-
B.
homeFacilityCity
Indicates the city in which an entity’s primary or home facility is located.
-
C.
homeFacilityUse
chosen
Indicates that an entity uses or is served by a particular home or primary facility as its main location for activities or services.
-
D.
homeFacilityName
Indicates the name of the primary facility or location that serves as the entity’s designated home base.
-
E.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626b2ba8c819090a9eb67cf9cb701 |
completed | May 2, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:43 a.m.