Triple
T10292627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democratic Federal Yugoslavia |
E241398
|
entity |
| Predicate | formedAtEvent |
P654
|
FINISHED |
| Object | second session of AVNOJ |
—
|
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: second session of AVNOJ | Statement: [Democratic Federal Yugoslavia, formedAtEvent, second session of AVNOJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAtEvent Context triple: [Democratic Federal Yugoslavia, formedAtEvent, second session of AVNOJ]
-
A.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
-
B.
posedAtEvent
Indicates that an entity assumed a particular pose or posture during a specified event.
-
C.
formationEvent
chosen
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
D.
formedWithin
Indicates that one entity was created, established, or came into existence inside the spatial or structural bounds of another entity.
-
E.
adoptedAtEvent
Indicates that an entity formally became an adopter or was officially adopted during a specific event.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d35f048190a215493acdf1f718 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.