Triple
T25956219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perinçek v. Switzerland |
E654106
|
entity |
| Predicate | partyTypeOfApplicant |
P9658
|
FINISHED |
| Object | individual |
—
|
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: individual | Statement: [Perinçek v. Switzerland, partyTypeOfApplicant, individual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyTypeOfApplicant Context triple: [Perinçek v. Switzerland, partyTypeOfApplicant, individual]
-
A.
partyTypeOfRespondent
Indicates the specific legal or procedural role that the respondent plays as a party in a case or proceeding.
-
B.
applicantType
chosen
Indicates the classification or category of an applicant in relation to an application or selection process.
-
C.
personType
Indicates that an entity is classified as a particular type or category of person.
-
D.
appliesToPersonType
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a certain type or category of person.
-
E.
namedPartyType
Indicates the specific role or category that a referenced party holds within a given context or relationship.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6049ef41c81908bace173136c2b00 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 8:45 a.m.