Triple
T23074426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salome Violetta Haertel |
E575288
|
entity |
| Predicate | hasAppearedWith |
P72473
|
FINISHED |
| Object | Alex Kingston |
—
|
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: Alex Kingston | Statement: [Salome Violetta Haertel, hasAppearedWith, Alex Kingston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAppearedWith Context triple: [Salome Violetta Haertel, hasAppearedWith, Alex Kingston]
-
A.
playedInEnsembleWith
Indicates that one entity has performed together with another as members of the same musical ensemble or group.
-
B.
playedAlongside
chosen
Indicates that two or more entities participated together at the same time in a shared activity, performance, or event.
-
C.
hasNotableMultipleAppearances
Indicates that an entity appears multiple times in a context or medium in a way considered significant or noteworthy.
-
D.
appearsAgainst
Indicates that one entity is visually or publicly presented in opposition to, or in contrast with, another entity.
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c61bb7c8190a3d9b1fba173cdff |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:56 p.m.