Triple

T34982420
Position Surface form Disambiguated ID Type / Status
Subject The Maquis, Part I E1008849 entity
Predicate introducesFictionalOrganization P22830 FINISHED
Object Maquis NE NERFINISHED

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: Maquis | Statement: [The Maquis, Part I, introducesFictionalOrganization, Maquis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducesFictionalOrganization
Context triple: [The Maquis, Part I, introducesFictionalOrganization, Maquis]
  • A. fictionalOrganizationFeatured chosen
    Indicates that a fictional organization is prominently presented or plays a significant role within a given work or context.
  • B. worksForFictionalOrganization
    Indicates that an entity is employed by or affiliated as a worker with a fictional organization.
  • C. setInFictionalOrganization
    Indicates that an entity is located within, associated with, or takes place inside a fictional organization.
  • D. fictionalOrganizationSponsor
    Indicates that one entity acts as a sponsor or patron for a fictional organization, providing support, endorsement, or resources to it.
  • E. fictionalCorporation
    Indicates that an entity is a corporation that exists only in fiction rather than in the real world.
  • 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_69f76dc844a48190881951fffb83d17e completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fe0d165a48819098b854318a50d76c completed May 8, 2026, 4:19 p.m.
PD Predicate disambiguation batch_69fe0931002481908a95b34f95e9f64e completed May 8, 2026, 4:02 p.m.
Created at: May 3, 2026, 4:01 p.m.