Triple
T30783247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsberg in Ostpreußen |
E783879
|
entity |
| Predicate | coordinatesSameAs |
P174737
|
FINISHED |
| Object | Górowo Iławeckie |
—
|
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: Górowo Iławeckie | Statement: [Landsberg in Ostpreußen, coordinatesSameAs, Górowo Iławeckie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesSameAs Context triple: [Landsberg in Ostpreußen, coordinatesSameAs, Górowo Iławeckie]
-
A.
coordinatesWith
Indicates that one entity works together with another in an organized or synchronized manner to achieve a shared or compatible outcome.
-
B.
coordinatesIn
Indicates that one entity specifies the spatial coordinates or position of another entity within a given reference frame or system.
-
C.
coordinatesWithin
Indicates that one set of coordinates lies entirely inside the spatial bounds defined by another.
-
D.
coordinateOn
Indicates that two or more entities work together to organize, align, or manage a shared activity, process, or objective.
-
E.
coordinateBetween
Indicates that one entity’s position or value lies between two other reference points within a coordinate system.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 29, 2026, 8:41 p.m.