Triple
T8232293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title I: Fundamental Rights and Duties |
E192321
|
entity |
| Predicate | endArticle |
P14519
|
FINISHED |
| Object | Article 55 |
—
|
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 55 | Statement: [Title I: Fundamental Rights and Duties, endArticle, Article 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endArticle Context triple: [Title I: Fundamental Rights and Duties, endArticle, Article 55]
-
A.
isFinalArticleOf
chosen
Indicates that one article is the concluding or last article within a defined sequence, series, or collection.
-
B.
editorEnd
Indicates that an entity serves as the ending or concluding editor for a work, marking the final editorial responsibility in its production.
-
C.
articleContent
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
-
D.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
E.
closingSection
Indicates that one entity serves as the concluding or final section of another entity (such as a document, event, or structured sequence).
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7824a6c48190a3abb76c4c3dcc71 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.