Triple
T29257765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Hutson Center |
E741749
|
entity |
| Predicate | primaryUserPosition |
P202934
|
FINISHED |
| Object | NFL players |
—
|
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: NFL players | Statement: [Don Hutson Center, primaryUserPosition, NFL players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUserPosition Context triple: [Don Hutson Center, primaryUserPosition, NFL players]
-
A.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
B.
primaryUserDesignation
Indicates that one user is designated as the main or primary user among multiple associated users.
-
C.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
D.
targetUserPosition
Indicates the spatial position or location of a specified user relative to a reference frame or environment.
-
E.
primaryUserIntended
Indicates that the referenced user is the main or originally intended user associated with the action, resource, or context.
- F. None of above. chosen
Provenance (4 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a00d24043e8819090cc473b6c0923d0 |
completed | May 10, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_6a00d1ec12fc81908c514ed088ef8300 |
completed | May 10, 2026, 6:43 p.m. |
| PDg | Predicate description generation | batch_6a00d23f402c8190bf49c0d4cce10b73 |
completed | May 10, 2026, 6:45 p.m. |
Created at: April 28, 2026, 12:39 p.m.