Triple

T5649373
Position Surface form Disambiguated ID Type / Status
Subject Taplow E124463 entity
Predicate hasDialogueFunction P65418 FINISHED
Object exposesCrockerHarrisReputationAmongPupils 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: exposesCrockerHarrisReputationAmongPupils | Statement: [Taplow, hasDialogueFunction, exposesCrockerHarrisReputationAmongPupils]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDialogueFunction
Context triple: [Taplow, hasDialogueFunction, exposesCrockerHarrisReputationAmongPupils]
  • A. hasProseDialogue
    Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
  • B. hasNoSpokenDialogue
    Indicates that the referenced entity does not produce any spoken dialogue within the given context or work.
  • C. hasSpeech
    Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
  • D. dialogueType
    Indicates the specific kind or category of dialogue occurring between entities (e.g., question-answer, negotiation, instruction).
  • E. hasVoiceIn
    Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
  • F. None of above. chosen

Provenance (4 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_69c00825df388190a58742fa9b1aa33d completed March 22, 2026, 3:17 p.m.
NER Named-entity recognition batch_69c022d2ed648190a5152c8668cbda02 completed March 22, 2026, 5:11 p.m.
PD Predicate disambiguation batch_69c01b2168508190b64b355cf50034ad completed March 22, 2026, 4:38 p.m.
PDg Predicate description generation batch_69c01f0727bc8190b16e9a669c04b4dd completed March 22, 2026, 4:55 p.m.
Created at: March 22, 2026, 3:42 p.m.