Triple
T35532967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laura Bellingham |
E1026852
|
entity |
| Predicate | roleInAmulet |
P191463
|
FINISHED |
| Object | cinematographer |
—
|
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: cinematographer | Statement: [Laura Bellingham, roleInAmulet, cinematographer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAmulet Context triple: [Laura Bellingham, roleInAmulet, cinematographer]
-
A.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
B.
roleInRings
Indicates the specific function or position an entity holds within one or more ring structures or ring-based systems.
-
C.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
D.
wielderRole
chosen
Indicates the specific role or function an entity has in relation to the item or power it wields.
-
E.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: May 3, 2026, 4:04 p.m.