Triple
T23648843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Pressure |
E584112
|
entity |
| Predicate | notableAppearanceOf |
P10205
|
FINISHED |
| Object | Lee Tracy |
—
|
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: Lee Tracy | Statement: [High Pressure, notableAppearanceOf, Lee Tracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAppearanceOf Context triple: [High Pressure, notableAppearanceOf, Lee Tracy]
-
A.
notableAppearanceIn
Indicates that an entity is prominently featured or plays a significant role in a particular work, event, or context.
-
B.
notableAppearance
chosen
Indicates that an entity is prominently featured or makes a significant appearance in another work, event, or context.
-
C.
notableAppearanceType
Indicates the type or category of a notable appearance associated with an entity, such as a significant role, cameo, or featured presence.
-
D.
notableDepictionBy
Indicates that an entity is significantly portrayed or represented by a particular creator, work, or medium.
-
E.
notableOwnerAppearsIn
Indicates that a notable owner of an entity appears within, or is featured in, another entity (such as a work, event, or medium).
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b287606881909926de5efd882a76 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.