Triple

T3344065
Position Surface form Disambiguated ID Type / Status
Subject Mary Doe E70327 entity
Predicate hasPseudonymRole P43812 FINISHED
Object plaintiff 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: plaintiff | Statement: [Mary Doe, hasPseudonymRole, plaintiff]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPseudonymRole
Context triple: [Mary Doe, hasPseudonymRole, plaintiff]
  • A. usedPseudonym
    Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
  • B. pseudonymCoinedBy
    Indicates that a particular pseudonym was created or invented by a specific agent or source.
  • C. pseudonymInspiredBy
    Indicates that a pseudonym was chosen or created based on, or in homage to, another name, person, work, or concept.
  • D. hasLegalRole chosen
    Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
  • E. hasMetafictionalRole
    Indicates that an entity plays a role within a story that self-consciously comments on, references, or breaks the conventions of fiction itself.
  • 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_69ad85a405e48190b6e68de7cf9f319e completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb1f23008819084ea68b8431c50ab completed March 8, 2026, 5:29 p.m.
PD Predicate disambiguation batch_69ada42df1d48190874bb05f95deefde completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:12 p.m.