Triple
T21224202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRVCC |
E523048
|
entity |
| Predicate | requiresSupportIn |
P84756
|
FINISHED |
| Object | user equipment |
—
|
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: user equipment | Statement: [SRVCC, requiresSupportIn, user equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSupportIn Context triple: [SRVCC, requiresSupportIn, user equipment]
-
A.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
isSupportedFor
Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
-
C.
requiresForFeature
chosen
Indicates that one entity must be present, implemented, or satisfied in order for a particular feature of another entity to be available or function correctly.
-
D.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
E.
requiresCapability
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734a9c9f88190817b574f916886e5 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.