Triple
T23574278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelers |
E580203
|
entity |
| Predicate | leadActorForCharacter_CarlyShannon |
P9616
|
FINISHED |
| Object | Nesta Cooper |
—
|
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: Nesta Cooper | Statement: [Travelers, leadActorForCharacter_CarlyShannon, Nesta Cooper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorForCharacter_CarlyShannon Context triple: [Travelers, leadActorForCharacter_CarlyShannon, Nesta Cooper]
-
A.
performerCharacterName
Indicates that a performer is associated with or portrays a specific character name in a performance or work.
-
B.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
characterPortrayedIs
Indicates that one entity serves as the fictional or dramatic role that is depicted or played by another entity.
-
D.
leadCharacterField
Indicates that one entity serves as the primary or main character associated with another entity, such as a work or production.
-
E.
leadActress
Indicates that the subject is the primary female performer in the specified film, show, or production.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd4cde48190b5e4eb162d772319 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:37 p.m.