Triple
T8755656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPPC |
E208065
|
entity |
| Predicate | mayBeExtendedBy |
P2150
|
FINISHED |
| Object | more advanced consent profiles |
—
|
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: more advanced consent profiles | Statement: [BPPC, mayBeExtendedBy, more advanced consent profiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeExtendedBy Context triple: [BPPC, mayBeExtendedBy, more advanced consent profiles]
-
A.
mayExtendTo
chosen
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
B.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
C.
extendsTo
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
D.
isExtendedVersionOf
Indicates that one entity is a longer or more developed form of another, typically adding content or features while preserving the original’s core.
-
E.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd95e9481909cc88e8d91601754 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.