Triple
T20067974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmire |
E499658
|
entity |
| Predicate | demonstratesTheme |
P202
|
FINISHED |
| Object | appearance versus reality |
—
|
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: appearance versus reality | Statement: [Elmire, demonstratesTheme, appearance versus reality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonstratesTheme Context triple: [Elmire, demonstratesTheme, appearance versus reality]
-
A.
exhibitTheme
Indicates that something (such as a work, event, or presentation) presents, embodies, or is organized around a particular theme.
-
B.
demonstratedBy
chosen
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
C.
performedThemeFor
Indicates that an agent carried out or executed a performance specifically for a particular theme or subject.
-
D.
demonstratedOn
Indicates that an action, behavior, or property is shown, illustrated, or proven using a particular entity as the example or subject.
-
E.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6637ac3fc8190911063b979c3afb8 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.