Triple
T441866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Draft |
E10130
|
entity |
| Predicate | primaryParticipants |
P6467
|
FINISHED |
| Object | NFL teams |
—
|
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 teams | Statement: [NFL Draft, primaryParticipants, NFL teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryParticipants Context triple: [NFL Draft, primaryParticipants, NFL teams]
-
A.
primaryBeneficiaries
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
-
B.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
C.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
E.
notableParticipant
chosen
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef42b4008190abed9d79926c7022 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.