Triple
T34533828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Assembly |
E886613
|
entity |
| Predicate | isKeyBodyWithin |
P33647
|
FINISHED |
| Object | Parliamentary Assembly of Turkic States |
—
|
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: Parliamentary Assembly of Turkic States | Statement: [Council of Assembly, isKeyBodyWithin, Parliamentary Assembly of Turkic States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyBodyWithin Context triple: [Council of Assembly, isKeyBodyWithin, Parliamentary Assembly of Turkic States]
-
A.
isKeyBodyOf
chosen
Indicates that one entity serves as the primary or central body/content component of another entity.
-
B.
isInBody
Indicates that one entity is physically contained within or located inside the body of another entity.
-
C.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
D.
isGlobalBodyOf
Indicates that one entity functions as the overarching, worldwide governing or coordinating body for another entity or domain.
-
E.
isKeyPartOf
Indicates that something functions as an essential component or crucial element within a larger whole.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.