Triple
T35279146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parx Publishing |
E1018883
|
entity |
| Predicate | workTypeManaged |
P150257
|
FINISHED |
| Object | music tracks |
—
|
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: music tracks | Statement: [Parx Publishing, workTypeManaged, music tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTypeManaged Context triple: [Parx Publishing, workTypeManaged, music tracks]
-
A.
projectTypeManaged
Indicates that an entity is responsible for overseeing or administering a particular type or category of project.
-
B.
workTypeOfSetting
Indicates the type or nature of work activity that characterizes or occurs within a particular setting.
-
C.
productTypeManaged
chosen
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type of product.
-
D.
grantedForWorkType
Indicates that a permission, license, or authorization is given specifically in connection with a particular type or category of work.
-
E.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd7c9148190848a6671583dc146 |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.