Triple
T407245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Court of Human Rights |
E9408
|
entity |
| Predicate | enteredFullTimeOperation |
P2339
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [European Court of Human Rights, enteredFullTimeOperation, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredFullTimeOperation Context triple: [European Court of Human Rights, enteredFullTimeOperation, 1998]
-
A.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
B.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
C.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
D.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
E.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbd766c8190bb8a91605929156a |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.