Triple
T22998664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic Circle |
E572577
|
entity |
| Predicate | parallelType |
P150562
|
FINISHED |
| Object | major circle of latitude |
—
|
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: major circle of latitude | Statement: [Arctic Circle, parallelType, major circle of latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelType Context triple: [Arctic Circle, parallelType, major circle of latitude]
-
A.
parallelismType
Indicates the specific kind or classification of parallel relationship that holds between two entities or processes.
-
B.
parallel
Indicates that two or more entities maintain a constant separation and direction without intersecting or converging.
-
C.
parallelCharacter
Indicates that one character corresponds to or mirrors another character in a parallel role, function, or narrative pattern.
-
D.
parallelPosition
Indicates that two entities occupy positions that are aligned in parallel relative to a reference frame or axis.
-
E.
parallelPassage
Indicates that one text segment corresponds closely in content or structure to another, such that they can be considered parallel versions or accounts of the same material.
- 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_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. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:50 p.m.