Triple
T29403545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Rockwell |
E745719
|
entity |
| Predicate | notableTypeOfRole |
P20971
|
FINISHED |
| Object | supporting roles |
—
|
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: supporting roles | Statement: [Jack Rockwell, notableTypeOfRole, supporting roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTypeOfRole Context triple: [Jack Rockwell, notableTypeOfRole, supporting roles]
-
A.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
-
B.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
C.
notableBearerOfRole
Indicates that an entity is a particularly prominent or well-known holder or performer of a specified role.
-
D.
notableCharacterType
chosen
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
E.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0358c946f08190a8fb41c643074475 |
completed | May 12, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_6a03586e5bb08190a71e075fde7cd679 |
completed | May 12, 2026, 4:42 p.m. |
Created at: April 28, 2026, 2:52 p.m.