Triple
T447157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Paris (1783) |
E7046
|
entity |
| Predicate | includedArticle |
P2947
|
FINISHED |
| Object | Article 1 recognizing US independence |
—
|
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: Article 1 recognizing US independence | Statement: [Treaty of Paris (1783), includedArticle, Article 1 recognizing US independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedArticle Context triple: [Treaty of Paris (1783), includedArticle, Article 1 recognizing US independence]
-
A.
containsArticle
chosen
Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
-
B.
keyArticle
Indicates that an article is a primary or central reference for understanding, supporting, or defining another entity or topic.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
E.
articleType
Indicates the specific category or kind of article associated with an entity.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef62c7a88190851fcd57658b4102 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.