Triple
T35598113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erieye |
E1028692
|
entity |
| Predicate | coverageArc |
P193090
|
FINISHED |
| Object | approximately 150 degrees per side |
—
|
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: approximately 150 degrees per side | Statement: [Erieye, coverageArc, approximately 150 degrees per side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverageArc Context triple: [Erieye, coverageArc, approximately 150 degrees per side]
-
A.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
B.
coverageBasis
Indicates the underlying principle, rule, or criteria on which a particular coverage or protection is determined or applied.
-
C.
coverageWindow
Indicates the time period or range during which coverage, protection, or applicability of something is in effect.
-
D.
cobertura
Indicates that one entity provides coverage, protection, or a covering layer over another entity.
-
E.
scaleCoverage
Indicates adjusting the extent or scope of coverage, typically by increasing or decreasing it according to some scale or demand.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 4:05 p.m.