Triple
T38222999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Rams, 1998–2001 |
E1012061
|
entity |
| Predicate | leftTackle |
P52799
|
FINISHED |
| Object | Orlando Pace |
—
|
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: Orlando Pace | Statement: [St. Louis Rams, 1998–2001, leftTackle, Orlando Pace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftTackle Context triple: [St. Louis Rams, 1998–2001, leftTackle, Orlando Pace]
-
A.
offensiveTackle
chosen
Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football context.
-
B.
defensiveTackle
Indicates that an entity plays the defensive tackle position, typically lining up on the interior of the defensive line to disrupt offensive plays.
-
C.
leftFielder
Indicates the relationship where an entity serves in the defensive baseball position of left fielder for a team or in a specific game context.
-
D.
leftFeature
Indicates that one entity functions as a feature or characteristic located on the left side of another entity.
-
E.
leftTeam
Indicates that an entity has departed from or is no longer a member of a particular team.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.