Triple
T23871511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron Mackintosh Ltd. |
E592739
|
entity |
| Predicate | licensingScope |
P41559
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Cameron Mackintosh Ltd., licensingScope, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensingScope Context triple: [Cameron Mackintosh Ltd., licensingScope, global]
-
A.
licenseScope
chosen
Indicates the specific rights, limitations, and conditions that define how and where a license may be used or applied.
-
B.
licensingRestriction
Indicates that there is a constraint or condition imposed on the use, distribution, or modification of something under a specific license.
-
C.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
D.
licensingBasisIncludes
Indicates that one licensing basis incorporates or contains another licensing basis as part of its governing conditions or requirements.
-
E.
licensingComponent
Indicates that one entity serves as a licensing-related component or module within the context or operation 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfe1f948190ad2c0d5bbe0c7240 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.