Triple
T11050275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encino Man |
E261225
|
entity |
| Predicate | hasCameoBy |
P49662
|
FINISHED |
| Object | Brendan Fraser as Link in other films |
—
|
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: Brendan Fraser as Link in other films | Statement: [Encino Man, hasCameoBy, Brendan Fraser as Link in other films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCameoBy Context triple: [Encino Man, hasCameoBy, Brendan Fraser as Link in other films]
-
A.
hasDirectorCameo
Indicates that the director of a work appears in a cameo role within that same work.
-
B.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
-
C.
featuresPerformerCameo
Indicates that the subject includes a brief, special appearance by a performer who is not part of the main cast or lineup.
-
D.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
-
E.
featuresCameoBy
chosen
Indicates that a work includes a brief, often special-appearance role performed by the specified person or entity.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79868c78881908c8e3672c05ae7ec |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.