Triple
T24791228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SJR |
E620254
|
entity |
| Predicate | underlyingCompanyServiceRegion |
P35149
|
FINISHED |
| Object | Northern Ontario |
—
|
NE NERFINISHED |
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: Northern Ontario | Statement: [SJR, underlyingCompanyServiceRegion, Northern Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyServiceRegion Context triple: [SJR, underlyingCompanyServiceRegion, Northern Ontario]
-
A.
underlyingCompanyService
chosen
Indicates that one entity functions as a foundational or supporting service for another company or business entity.
-
B.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
C.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
D.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
-
E.
underlyingCompanyProvides
Indicates that an underlying company supplies or makes available a product, service, or resource to another party or entity.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 4:47 a.m.