Triple
T19070102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby sevens |
E466768
|
entity |
| Predicate | contact |
P19362
|
FINISHED |
| Object | full-contact |
—
|
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: full-contact | Statement: [Rugby sevens, contact, full-contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contact Context triple: [Rugby sevens, contact, full-contact]
-
A.
contactWith
chosen
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
B.
contactLanguageWith
Indicates that two entities communicate with each other using a particular language as the medium of contact.
-
C.
earlyContact
Indicates that one entity initiates contact with another earlier than a typical, expected, or reference time.
-
D.
technicalContact
Indicates that one entity serves as the primary point of contact for technical issues, support, or maintenance related to another entity.
-
E.
contactPolicy
Indicates the rules or constraints governing how and when one party is allowed to initiate or maintain contact with another.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19ea01c8190b9bb789da32f9a90 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.