Triple
T34249193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Bridges as Matt Scudder |
E878690
|
entity |
| Predicate | screenCharacterStatus |
P129147
|
FINISHED |
| Object | ex-cop |
—
|
LITERAL FINISHED |
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: ex-cop | Statement: [Jeff Bridges as Matt Scudder, screenCharacterStatus, ex-cop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenCharacterStatus Context triple: [Jeff Bridges as Matt Scudder, screenCharacterStatus, ex-cop]
-
A.
screenCharacterBy
Indicates a relationship where one entity evaluates or selects characters according to certain criteria or standards.
-
B.
featuresCharacterWithStatus
chosen
Indicates that something (such as a work or scene) includes a character who has a specified status or condition.
-
C.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
D.
currentCharacter
Indicates that an entity is the character presently in focus or being actively considered in a given context or sequence.
-
E.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:56 a.m.