Triple
T34141523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPP over ATM |
E875730
|
entity |
| Predicate | isUsedBetween |
P17799
|
FINISHED |
| Object | customer premises equipment and DSLAM |
—
|
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: customer premises equipment and DSLAM | Statement: [PPP over ATM, isUsedBetween, customer premises equipment and DSLAM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedBetween Context triple: [PPP over ATM, isUsedBetween, customer premises equipment and DSLAM]
-
A.
usedBetween
chosen
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
-
B.
appliesBetween
Indicates that a specified condition, rule, or relationship holds specifically between two or more entities, rather than for each entity individually.
-
C.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
D.
currentBetween
Indicates that the current value of a quantity lies within a specified range between two boundary values.
-
E.
isCrossBetween
Indicates that one entity is a hybrid or intermediate form resulting from the combination or mixing of two other entities.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.