Triple

T16601476
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Madrid (1750) E403339 entity
Predicate articleIncluded P2947 FINISHED
Object provisions for boundary commissions 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: provisions for boundary commissions | Statement: [Treaty of Madrid (1750), articleIncluded, provisions for boundary commissions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: articleIncluded
Context triple: [Treaty of Madrid (1750), articleIncluded, provisions for boundary commissions]
  • A. articleContent
    Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
  • B. containsArticle chosen
    Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
  • C. textsIncludedIn
    Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
  • D. articleReference
    Indicates that one entity cites, mentions, or refers to another entity within an article or written document.
  • E. containsArticleOn
    Indicates that one entity includes or features an article about another entity within its content or collection.
  • 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35d764574819081366374ca0c9bea completed April 18, 2026, 10:31 a.m.
PD Predicate disambiguation batch_69e296aabc508190b3836a91b49113ad completed April 17, 2026, 8:23 p.m.
Created at: April 10, 2026, 5:17 a.m.