Triple
T29321828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General of the Resistance |
E743534
|
entity |
| Predicate | portrayedByActorOfHolder |
P1507
|
FINISHED |
| Object | Carrie Fisher |
—
|
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: Carrie Fisher | Statement: [General of the Resistance, portrayedByActorOfHolder, Carrie Fisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedByActorOfHolder Context triple: [General of the Resistance, portrayedByActorOfHolder, Carrie Fisher]
-
A.
portrayedBy
chosen
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
B.
portrayedByAlsoPlays
Indicates that the actor who portrays a given character also plays another specified role or character.
-
C.
portrayedByAlsoKnownFor
Indicates that an entity is portrayed by a person who is also notably known for another specific role or work.
-
D.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
E.
portrayedBySpeciesActor
Indicates that an entity is depicted or represented by an actor belonging to a particular species.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 28, 2026, 1:23 p.m.