Triple
T29895646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Adventures series |
E759269
|
entity |
| Predicate | licenceHolder |
P12714
|
FINISHED |
| Object | BBC |
—
|
NE NERFINISHED |
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: BBC | Statement: [New Adventures series, licenceHolder, BBC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenceHolder Context triple: [New Adventures series, licenceHolder, BBC]
-
A.
licenceAuthority
Indicates that one entity has the official power or jurisdiction to grant, issue, or regulate licences for another entity or activity.
-
B.
typeOfLicense
Indicates the specific kind or category of license associated with an entity.
-
C.
licenceBuiltIn
Indicates that a licence is inherently included within or comes pre-installed as part of another product, system, or component rather than being added separately.
-
D.
licenceCode
Indicates that one entity is associated with a specific license identifier or code that governs its permitted use or distribution.
-
E.
hasLicense
chosen
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 6:04 p.m.