Triple

T37565781
Position Surface form Disambiguated ID Type / Status
Subject Gwindor E933949 entity
Predicate disagreedWith P107359 FINISHED
Object Túrin Turambar’s war policy in Nargothrond 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: Túrin Turambar’s war policy in Nargothrond | Statement: [Gwindor, disagreedWith, Túrin Turambar’s war policy in Nargothrond]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: disagreedWith
Context triple: [Gwindor, disagreedWith, Túrin Turambar’s war policy in Nargothrond]
  • A. disputed
    Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
  • B. opposedBecause
    Indicates that one entity is opposed to another specifically due to a particular reason, cause, or justification.
  • C. disapprovedOf chosen
    Indicates that one entity holds a negative judgment or lack of approval toward another entity or that entity’s actions.
  • D. opposedBy
    Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
  • E. positionOnDisagreement
    Indicates the stance or viewpoint an entity holds regarding a particular disagreement or conflict.
  • 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_69f76ecb4acc8190b53f96d0b013e415 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba61dff5081909fec88a7aeb0c8a1 completed May 6, 2026, 8:35 p.m.
PD Predicate disambiguation batch_69fba350e9a8819095893229d9643572 completed May 6, 2026, 8:23 p.m.
Created at: May 3, 2026, 4:17 p.m.