Triple
T28080535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Józef Piłsudski’s federation concept (Międzymorze) |
E709662
|
entity |
| Predicate | aimedToInclude |
P164025
|
FINISHED |
| Object | Lithuania |
—
|
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: Lithuania | Statement: [Józef Piłsudski’s federation concept (Międzymorze), aimedToInclude, Lithuania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToInclude Context triple: [Józef Piłsudski’s federation concept (Międzymorze), aimedToInclude, Lithuania]
-
A.
aimedToInclude
chosen
Indicates that one entity intentionally sought to have another entity or element contained or incorporated within it.
-
B.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
C.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
-
D.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:51 p.m.