Triple
T31534355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadezhda von Meck |
E804563
|
entity |
| Predicate | meetingPolicyWithTchaikovsky |
P44676
|
FINISHED |
| Object | never met in person by mutual agreement |
—
|
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: never met in person by mutual agreement | Statement: [Nadezhda von Meck, meetingPolicyWithTchaikovsky, never met in person by mutual agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingPolicyWithTchaikovsky Context triple: [Nadezhda von Meck, meetingPolicyWithTchaikovsky, never met in person by mutual agreement]
-
A.
meetingPeriod
Indicates the time span or duration during which a meeting takes place.
-
B.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
C.
meetingContext
chosen
Indicates the situational setting, circumstances, or background conditions in which a meeting takes place.
-
D.
meetingLevel
Indicates the degree or intensity of interaction or engagement between participants in a meeting or meeting-like context.
-
E.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:02 p.m.