Triple
T7404339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Consumer Protection |
E170828
|
entity |
| Predicate | contactMethod |
P41776
|
FINISHED |
| Object | consumer hotline |
—
|
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: consumer hotline | Statement: [Division of Consumer Protection, contactMethod, consumer hotline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactMethod Context triple: [Division of Consumer Protection, contactMethod, consumer hotline]
-
A.
contactLanguageWith
Indicates that two entities communicate with each other using a particular language as the medium of contact.
-
B.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
C.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
D.
hasContactMethod
chosen
Indicates that an entity has a specific way or channel through which it can be contacted.
-
E.
consultationMethod
Indicates the way or medium through which a consultation is conducted or delivered.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2701b108190be39174d4534f231 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.