Triple
T286813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFTP |
E5902
|
entity |
| Predicate | notSuitableFor |
P7029
|
FINISHED |
| Object | high-latency 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: high-latency networks | Statement: [TFTP, notSuitableFor, high-latency networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notSuitableFor Context triple: [TFTP, notSuitableFor, high-latency networks]
-
A.
notTypicallyUsedFor
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
B.
doesNotServe
Indicates that one entity explicitly does not provide a service, function, or role to another entity.
-
C.
doesNotGenerallyApplyTo
chosen
Indicates that a rule, property, or condition is typically not relevant or applicable to the referenced entity or situation in most cases.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
isNotRequiredFor
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.