Triple
T19165470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phil Petrillo |
E469166
|
entity |
| Predicate | appearsOffScreen |
P134685
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Phil Petrillo, appearsOffScreen, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOffScreen Context triple: [Phil Petrillo, appearsOffScreen, true]
-
A.
hasOnScreenDynamic
Indicates that one entity displays or presents another entity as a changing or interactive element on a screen.
-
B.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
-
C.
onScreenDynamicWith
Indicates that two entities are simultaneously visible and interacting or changing together within the same on-screen context.
-
D.
appearTo
Indicates that something gives the impression or seems to be a certain way to an observer, without confirming that it actually is so.
-
E.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
- F. None of above. chosen
Provenance (4 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f15ee064819087f9fd822236298f |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.