Triple
T13206137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tramp |
E314363
|
entity |
| Predicate | featuresDialogue |
P95630
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tramp, featuresDialogue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDialogue Context triple: [Tramp, featuresDialogue, true]
-
A.
hasDialogueTrait
Indicates that an entity possesses a specific characteristic or quality related to dialogue or conversational behavior.
-
B.
hasDialogueIn
chosen
Indicates that an entity participates in or contains spoken or written dialogue within a specified context, such as a scene, work, or medium.
-
C.
dialogueType
Indicates the specific kind or category of dialogue occurring between entities (e.g., question-answer, negotiation, instruction).
-
D.
dialoguesBy
Indicates that one entity is the creator, author, or source of the dialogues associated with another entity.
-
E.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9b0cf08190a1d71cc94139539d |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.