Triple
T2714481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taxpayer Advocate Service |
E59935
|
entity |
| Predicate | hasContactMethod |
P41776
|
FINISHED |
| Object | telephone |
—
|
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: telephone | Statement: [Taxpayer Advocate Service, hasContactMethod, telephone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactMethod Context triple: [Taxpayer Advocate Service, hasContactMethod, telephone]
-
A.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
-
B.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
-
C.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
D.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
E.
hasTeleconnectionsWith
Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
- F. None of above. chosen
Provenance (4 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda93a2388190b55a1c821ef6bc64 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd949c120819099a9d56eb71a0339 |
completed | March 7, 2026, 7:52 a.m. |
Created at: March 6, 2026, 9:55 p.m.