Triple
T32190786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaanbaaz |
E822235
|
entity |
| Predicate | specialAppearanceBy |
P48259
|
FINISHED |
| Object | Sridevi |
—
|
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: Sridevi | Statement: [Jaanbaaz, specialAppearanceBy, Sridevi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialAppearanceBy Context triple: [Jaanbaaz, specialAppearanceBy, Sridevi]
-
A.
specialAppearance
chosen
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
-
B.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
C.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
-
D.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
E.
specialEventServiceTo
Indicates that a service is specifically provided or designated for a particular special event.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 12:35 a.m.