Triple
T16743429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sierra magazine |
E406888
|
entity |
| Predicate | alsoCoversRegion |
P13946
|
FINISHED |
| Object | global environmental issues |
—
|
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: global environmental issues | Statement: [Sierra magazine, alsoCoversRegion, global environmental issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCoversRegion Context triple: [Sierra magazine, alsoCoversRegion, global environmental issues]
-
A.
alsoCovers
chosen
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
B.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
C.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
D.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa205138819080284fd9a4341225 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.