Triple
T7223493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protocol No. 1 to the European Convention on Human Rights |
E150318
|
entity |
| Predicate | article1Title |
P38
|
FINISHED |
| Object | Protection of property |
—
|
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: Protection of property | Statement: [Protocol No. 1 to the European Convention on Human Rights, article1Title, Protection of property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: article1Title Context triple: [Protocol No. 1 to the European Convention on Human Rights, article1Title, Protection of property]
-
A.
title
chosen
Indicates that one entity serves as the formal name or designation of another entity.
-
B.
article1ContentSummary
Indicates a brief, condensed representation of the main points or key information contained in the first article’s content.
-
C.
textTitle
Indicates that one text entity serves as the title or heading for another text or resource.
-
D.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
E.
articleContent
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b54a5c8190a4a289f32853a8fe |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.