Triple
T19464576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mantrap (1926 film) |
E486958
|
entity |
| Predicate | featuredPerformerType |
P101716
|
FINISHED |
| Object | flapper icon |
—
|
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: flapper icon | Statement: [Mantrap (1926 film), featuredPerformerType, flapper icon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredPerformerType Context triple: [Mantrap (1926 film), featuredPerformerType, flapper icon]
-
A.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
featuresPerformerType
chosen
Indicates that something includes or highlights a performer of a specified type (e.g., musician, actor, or other performance role).
-
C.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
D.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
E.
featuresPerformerCameo
Indicates that the subject includes a brief, special appearance by a performer who is not part of the main cast or lineup.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633d0fe3c8190b637f78bfad704d0 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.