Triple
T7492444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POTS (Plain Old Telephone Service) |
E177036
|
entity |
| Predicate | usesRingingVoltage |
P77849
|
FINISHED |
| Object | approximately 70–90 V AC |
—
|
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: approximately 70–90 V AC | Statement: [POTS (Plain Old Telephone Service), usesRingingVoltage, approximately 70–90 V AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRingingVoltage Context triple: [POTS (Plain Old Telephone Service), usesRingingVoltage, approximately 70–90 V AC]
-
A.
ringingMethod
Indicates that one entity uses or is associated with a specific method or pattern for ringing (such as in bell-ringing or similar signaling activities).
-
B.
hasRingConfiguration
Indicates that one entity possesses or exhibits a specific arrangement or pattern of rings in its structure or form.
-
C.
numberOfRings
Indicates the quantity of rings associated with an entity.
-
D.
hasBells
Indicates that an entity possesses or is equipped with one or more bells.
-
E.
usesEchoCancellation
Indicates that an entity employs echo cancellation techniques to reduce or eliminate echo in audio communication.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:43 p.m.