Triple
T22998697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polar Circles |
E572577
|
entity |
| Predicate | separate |
P1175
|
FINISHED |
| Object | mid-latitudes from polar regions |
—
|
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: mid-latitudes from polar regions | Statement: [Polar Circles, separate, mid-latitudes from polar regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separate Context triple: [Polar Circles, separate, mid-latitudes from polar regions]
-
A.
separates
chosen
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
B.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
C.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
-
D.
separatedAlongWith
Indicates that an entity becomes separated from something while simultaneously being accompanied or grouped with another specified entity during the separation.
-
E.
separatesState
Indicates that one entity serves as a dividing boundary or barrier between two distinct states or regions.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f54ce88190930530958e2a1830 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.