Triple
T7492477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POTS (Plain Old Telephone Service) |
E177036
|
entity |
| Predicate | decliningDueTo |
P41905
|
FINISHED |
| Object | migration to mobile telephony |
—
|
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: migration to mobile telephony | Statement: [POTS (Plain Old Telephone Service), decliningDueTo, migration to mobile telephony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decliningDueTo Context triple: [POTS (Plain Old Telephone Service), decliningDueTo, migration to mobile telephony]
-
A.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
B.
decliningAs
Indicates that one entity is decreasing in value, intensity, or importance relative to another over time.
-
C.
declineTriggeredBy
chosen
Indicates that a decline event or state is caused or initiated by a specified triggering factor or condition.
-
D.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
E.
decline
Indicates a decrease or reduction in the level, amount, quality, or intensity of something over time.
- 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_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. |
Created at: March 27, 2026, 3:43 p.m.