Triple
T515977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Engineering Steering Group |
E10706
|
entity |
| Predicate | emailContact |
P2798
|
FINISHED |
| Object | [email protected] |
—
|
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: [email protected] | Statement: [Internet Engineering Steering Group, emailContact, [email protected]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emailContact Context triple: [Internet Engineering Steering Group, emailContact, [email protected]]
-
A.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
B.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
C.
addressFormFor
Indicates the form of address or mode of speaking that one entity should use when referring to or speaking to another entity.
-
D.
officeNumber
Indicates the specific room or suite number assigned to an office within a building or complex.
-
E.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1836b688190a60cc901a8724159 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.