Triple
T13626672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Colts offense |
E325599
|
entity |
| Predicate | receiverNumber |
P5467
|
FINISHED |
| Object | 82 |
—
|
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: 82 | Statement: [Baltimore Colts offense, receiverNumber, 82]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receiverNumber Context triple: [Baltimore Colts offense, receiverNumber, 82]
-
A.
receiverType
Indicates the category or classification of the entity that receives something (such as a message, resource, or action) in the relationship.
-
B.
directiveNumber
Indicates the identifying number assigned to a specific directive or formal instruction within a set of directives.
-
C.
associatedNumber
chosen
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
D.
terminalNumber
Indicates the specific terminal identifier associated with an entity, such as a device, port, or connection point, within a larger system or network.
-
E.
radioTelephonyDesignatorFor
Indicates that one entity is the assigned radiotelephony (spoken) call sign or designator used in radio communications for 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.