Triple
T32036394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Dinner with Andre |
E818105
|
entity |
| Predicate | dialoguePercentage |
P65931
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [My Dinner with Andre, dialoguePercentage, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialoguePercentage Context triple: [My Dinner with Andre, dialoguePercentage, very high]
-
A.
dialogueLevel
chosen
Indicates the degree or intensity of conversational interaction occurring between entities.
-
B.
dialoguePosition
Indicates the relative placement or ordering of an utterance or turn within a dialogue or conversational sequence.
-
C.
numberOfDialogues
Indicates the total count of dialogues associated with or occurring between the referenced entities.
-
D.
dialogueDominance
Indicates that one participant exerts greater control or influence over the flow, topics, or outcomes of a dialogue than the other(s).
-
E.
dialogueFeature
Indicates that one entity exhibits or involves a particular characteristic, property, or element of a dialogue or conversational exchange with another entity.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49b23448190a6c600187b66c7c7 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:18 a.m.