Triple
T31937913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet War Memorial (Treptower Park) |
E815440
|
entity |
| Predicate | hasAxisOrientation |
P12663
|
FINISHED |
| Object | north–south |
—
|
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: north–south | Statement: [Soviet War Memorial (Treptower Park), hasAxisOrientation, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAxisOrientation Context triple: [Soviet War Memorial (Treptower Park), hasAxisOrientation, north–south]
-
A.
hasAxisConfiguration
Indicates that one entity specifies or defines the axis arrangement, orientation, or setup used by another entity.
-
B.
hasOrientation
chosen
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
C.
hasAxisCount
Indicates that an entity is associated with a specified number of axes.
-
D.
hasOrientationInUse
Indicates that an entity, when in use or operation, is oriented in a specific direction or spatial alignment.
-
E.
isAxisDirection
Indicates that one direction is aligned with or corresponds to a principal axis (such as x, y, or z) in a given coordinate system.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b26d4b5c8190bde4c96bf1860698 |
completed | May 3, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:05 a.m.