Triple
T25139788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambush |
E629768
|
entity |
| Predicate | leadActorForCharacterWardKinsman |
P141148
|
FINISHED |
| Object | Robert Taylor |
—
|
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: Robert Taylor | Statement: [Ambush, leadActorForCharacterWardKinsman, Robert Taylor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorForCharacterWardKinsman Context triple: [Ambush, leadActorForCharacterWardKinsman, Robert Taylor]
-
A.
worksForCharacterPlayedBy
Indicates that one character is employed by, or works under, another character who is portrayed by a specific actor.
-
B.
leadCharacterCaste
Indicates that the lead character in a work belongs to a specified caste.
-
C.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
D.
leadActorRolePattern
Indicates a recurring or characteristic type of role that an actor typically plays as a leading performer in productions.
-
E.
leadActorForCharacterLance
chosen
Indicates that the referenced person is the primary actor who portrays the character named Lance.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f468475218819089b73a0d2e072110 |
completed | May 1, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:29 a.m.