Triple
T18294131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frame Relay |
E438186
|
entity |
| Predicate | commonlyCarries |
P39152
|
FINISHED |
| Object | IP traffic |
—
|
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: IP traffic | Statement: [Frame Relay, commonlyCarries, IP traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyCarries Context triple: [Frame Relay, commonlyCarries, IP traffic]
-
A.
alsoCarries
Indicates that an entity, in addition to other items or responsibilities it has, carries another specified item or load as well.
-
B.
isCarrierOf
Indicates that one entity serves as the bearer, holder, or transmitter of another entity (such as an object, substance, trait, or information).
-
C.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
D.
typicallyHolds
chosen
Indicates that a certain relationship or condition generally holds true in typical or normal situations, though not necessarily in all cases.
-
E.
isMajorCarrierOf
Indicates that one entity serves as the primary or principal transporter or conveyor of another entity (such as goods, signals, or passengers).
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5010205bc8190a32fe731ead3d988 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.