Triple
T2150275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Poland |
E47162
|
entity |
| Predicate | officiallyAdopted |
P36255
|
FINISHED |
| Object | 1919-08-01 |
—
|
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: 1919-08-01 | Statement: [Flag of Poland, officiallyAdopted, 1919-08-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiallyAdopted Context triple: [Flag of Poland, officiallyAdopted, 1919-08-01]
-
A.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
-
B.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
C.
adoptiveNomen
Indicates a naming relationship where one entity has taken on or been given the name of another in an adoptive or non-biological sense.
-
D.
laterAdoptedBy
Indicates that one entity is adopted by another entity at a later point in time, after some prior state or relationship has already been established.
-
E.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe45dbf481909c0da056a1a99ece |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:44 p.m.