Triple
T24893050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETS No. 177 |
E623057
|
entity |
| Predicate | adoptedInFrameworkOf |
P157777
|
FINISHED |
| Object | Council of Europe |
—
|
NE NERFINISHED |
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: Council of Europe | Statement: [ETS No. 177, adoptedInFrameworkOf, Council of Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedInFrameworkOf Context triple: [ETS No. 177, adoptedInFrameworkOf, Council of Europe]
-
A.
adoptedFrameworkType
Indicates that one entity has chosen and is using a particular framework type as its adopted standard or approach.
-
B.
administeredWithinFrameworkOf
Indicates that an action or process is carried out under, and in accordance with, a specified framework, system, or governing structure.
-
C.
adoptedAsPartOf
Indicates that one entity has been taken in, integrated, or accepted as a component or member within another entity or larger whole.
-
D.
adoptedInForm
Indicates that something is accepted, implemented, or brought into use within a particular form, format, or structural arrangement.
-
E.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
- F. None of above. chosen
Provenance (4 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:26 a.m.