Triple
T24930220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exclusive Networks |
E618962
|
entity |
| Predicate | addsValueBy |
P157245
|
FINISHED |
| Object | technical support |
—
|
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: technical support | Statement: [Exclusive Networks, addsValueBy, technical support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsValueBy Context triple: [Exclusive Networks, addsValueBy, technical support]
-
A.
addsOverBase
Indicates that something is added on top of an existing base amount, value, or structure.
-
B.
increasesWith
Indicates that as the value or magnitude of one entity grows, the value or magnitude of another entity correspondingly grows as well.
-
C.
associatedValue
Indicates that one entity is linked to another entity that serves as its corresponding or contextually related value.
-
D.
laterAdditionsBy
Indicates that one entity consists of or represents additions or modifications that were made to another entity at a later time.
-
E.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
- F. None of above. chosen
Provenance (4 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f423b3b3408190bd586454c2cf9be7 |
completed | May 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:29 a.m.