Triple
T9403389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-root |
E226528
|
entity |
| Predicate | locatedInNetworkRegion |
P65282
|
FINISHED |
| Object | global |
—
|
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 | Statement: [I-root, locatedInNetworkRegion, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNetworkRegion Context triple: [I-root, locatedInNetworkRegion, global]
-
A.
networkRegion
chosen
Indicates that an entity belongs to, operates within, or is associated with a specific network-defined geographic or logical region.
-
B.
locatedInUSRegion
Indicates that one entity is geographically situated within a specified region of the United States.
-
C.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
D.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
E.
isInSameRegionAs
Indicates that two entities are located within the same defined geographic or administrative region.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51bf7e5c8190850b671778496150 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.