Triple
T5480046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VoLTE |
E123445
|
entity |
| Predicate | deploymentStarted |
P11880
|
FINISHED |
| Object | early 2010s |
—
|
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: early 2010s | Statement: [VoLTE, deploymentStarted, early 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentStarted Context triple: [VoLTE, deploymentStarted, early 2010s]
-
A.
deploymentTime
chosen
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
deploymentRequires
Indicates that performing a particular deployment is contingent upon the prior existence, completion, or availability of another specified resource, condition, or action.
-
C.
hasDeployment
Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
-
D.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
E.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.