Triple
T8136849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Shield |
E189992
|
entity |
| Predicate | structuralTrend |
P80880
|
FINISHED |
| Object | northwest‑southeast |
—
|
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: northwest‑southeast | Statement: [Ukrainian Shield, structuralTrend, northwest‑southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralTrend Context triple: [Ukrainian Shield, structuralTrend, northwest‑southeast]
-
A.
structuralIssues
Indicates that there are problems or deficiencies in the design, construction, or integrity of a structure or system.
-
B.
structureFocus
Indicates that attention or emphasis is placed on the structural aspects or organization of something within the described context.
-
C.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
D.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
traditionalStructure
Indicates that something follows or embodies a customary, historically established form, pattern, or organizational framework.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb440171d48190afa4a312ab19389c |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39d20e78819092ea9e04357be008 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:35 p.m.