Triple
T30690075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapphire & Steel |
E781299
|
entity |
| Predicate | leadActorForCharacter Steel |
P180541
|
FINISHED |
| Object | David McCallum |
—
|
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: David McCallum | Statement: [Sapphire & Steel, leadActorForCharacter Steel, David McCallum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorForCharacter Steel Context triple: [Sapphire & Steel, leadActorForCharacter Steel, David McCallum]
-
A.
leadRoleActor
Indicates that an actor performs a leading or principal role in a work or production.
-
B.
leadActorForCharacterLance
Indicates that the referenced person is the primary actor who portrays the character named Lance.
-
C.
leadActorForCharacter Philip Shayne
Indicates that the specified person is the primary actor portraying the character Philip Shayne.
-
D.
worksForCharacterPlayedBy
Indicates that one character is employed by, or works under, another character who is portrayed by a specific actor.
-
E.
leadActorRolePattern
Indicates a recurring or characteristic type of role that an actor typically plays as a leading performer in productions.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 29, 2026, 8:33 p.m.