Triple
T34541746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIGTRAN |
E886822
|
entity |
| Predicate | supportsMigrationTo |
P78933
|
FINISHED |
| Object | all‑IP telecom networks |
—
|
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: all‑IP telecom networks | Statement: [SIGTRAN, supportsMigrationTo, all‑IP telecom networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMigrationTo Context triple: [SIGTRAN, supportsMigrationTo, all‑IP telecom networks]
-
A.
supportsMigrationOf
chosen
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
-
B.
enabledMigrationOf
Indicates that one entity made it possible for another entity to move, transfer, or transition from one state, location, or system to another.
-
C.
supportsTransitionTo
Indicates that one state, condition, or entity enables or is compatible with moving or changing to another state, condition, or entity.
-
D.
hasReasonForMigration
Indicates that there exists a specific cause, motive, or justification for an entity’s act of migrating from one place to another.
-
E.
supportsUpgrade
Indicates that one entity is capable of accepting, enabling, or being compatible with an upgrade provided by another entity.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.