Triple
T7323503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gołdap |
E168809
|
entity |
| Predicate | joinedTo |
P4097
|
FINISHED |
| Object | Poland after World War II |
—
|
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: Poland after World War II | Statement: [Gołdap, joinedTo, Poland after World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedTo Context triple: [Gołdap, joinedTo, Poland after World War II]
-
A.
joinedPluralityBy
Indicates that multiple entities collectively became members or participants of the same group, organization, or event through a shared act of joining.
-
B.
joinedByInPart
Indicates that multiple entities are connected or associated together through a shared participation in a specific part or component of something.
-
C.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
D.
memberOf
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
E.
addedTo
chosen
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f046b93c8190a80dd48ee409ec5d |
completed | March 27, 2026, 9:01 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.