Triple
T34251905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle-earth Enterprises |
E878770
|
entity |
| Predicate | managesRightsScope |
P107177
|
FINISHED |
| Object | Middle-earth works |
—
|
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: Middle-earth works | Statement: [Middle-earth Enterprises, managesRightsScope, Middle-earth works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesRightsScope Context triple: [Middle-earth Enterprises, managesRightsScope, Middle-earth works]
-
A.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
B.
managesResourceType
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type or category of resource.
-
C.
namingRightsScope
chosen
Indicates the extent or boundaries of what an entity’s naming rights cover within a particular agreement or context.
-
D.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
E.
accessManagedBy
Indicates that control over access to a resource or system is administered or governed by a specified managing 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 1:56 a.m.