Triple
T38382911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatican Shadow |
E893800
|
entity |
| Predicate | labelRunByCreator |
P190821
|
FINISHED |
| Object | Hospital Productions |
—
|
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: Hospital Productions | Statement: [Vatican Shadow, labelRunByCreator, Hospital Productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelRunByCreator Context triple: [Vatican Shadow, labelRunByCreator, Hospital Productions]
-
A.
appliesToCreator
Indicates that something (such as a rule, condition, or attribute) is specifically relevant or applicable to the creator of an entity.
-
B.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
C.
creatorOwnership
Indicates that an entity is the original creator of something and holds ownership rights over it.
-
D.
describedByCreatorAs
Indicates that an entity is characterized or defined in a particular way according to the creator’s own description.
-
E.
possibleCreator
Indicates that an entity is a plausible but not definitively confirmed creator or originator of another entity.
- F. None of above. chosen
Provenance (4 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.