Triple
T35833031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mel Blount rule |
E1035850
|
entity |
| Predicate | contactRestriction |
P140207
|
FINISHED |
| Object | no significant contact with receiver beyond 5 yards |
—
|
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: no significant contact with receiver beyond 5 yards | Statement: [Mel Blount rule, contactRestriction, no significant contact with receiver beyond 5 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactRestriction Context triple: [Mel Blount rule, contactRestriction, no significant contact with receiver beyond 5 yards]
-
A.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
B.
worksAsContactFor
Indicates that one entity serves as the designated contact person or liaison for another entity.
-
C.
contactLanguageWith
Indicates that two entities communicate with each other using a particular language as the medium of contact.
-
D.
campaignRestriction
Indicates that there are specific rules or limitations governing how a campaign can be conducted, targeted, or configured.
-
E.
fieldRestriction
chosen
Indicates that access to or use of a particular field, area, or domain is limited or constrained by specified rules or conditions.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00d508290081909f3d5dfbb2e80c8e |
completed | May 10, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_6a00d49da4cc81909566ad286ec22292 |
completed | May 10, 2026, 6:55 p.m. |
Created at: May 3, 2026, 4:06 p.m.