Triple
T28793435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fannius |
E727020
|
entity |
| Predicate | discourseFunction |
P160899
|
FINISHED |
| Object | interlocutor in dialogue |
—
|
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: interlocutor in dialogue | Statement: [Fannius, discourseFunction, interlocutor in dialogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discourseFunction Context triple: [Fannius, discourseFunction, interlocutor in dialogue]
-
A.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
B.
discourseType
Indicates the specific kind or category of discourse (such as narrative, argument, explanation, or dialogue) that characterizes a given communicative act or text.
-
C.
placeInDiscourse
chosen
Indicates the position or role that an element occupies within the structure or flow of a discourse or conversation.
-
D.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
E.
discussionPublic
Indicates that a discussion is accessible to the general public rather than being restricted or private.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 6:24 a.m.