Triple
T25303198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Towson Tigers men's basketball (assistant coach) |
E634406
|
entity |
| Predicate | worksAtFacility |
P134061
|
FINISHED |
| Object | SECU Arena |
—
|
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: SECU Arena | Statement: [Towson Tigers men's basketball (assistant coach), worksAtFacility, SECU Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAtFacility Context triple: [Towson Tigers men's basketball (assistant coach), worksAtFacility, SECU Arena]
-
A.
worksAtSite
chosen
Indicates that an entity performs its job or duties at a particular physical site or location.
-
B.
workAt
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
-
C.
worksInDepartment
Indicates that an entity is employed in and performs their job duties within a particular department.
-
D.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
-
E.
worksAtBranch
Indicates that an individual is employed at and performs their job duties at a specific branch of an organization.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:25 p.m.