Triple
T306789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Internet Registries |
E6320
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | ARIN |
E38041
|
NE 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: ARIN | Statement: [Regional Internet Registries, includes, ARIN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ARIN Context triple: [Regional Internet Registries, includes, ARIN]
-
A.
ARIN
chosen
ARIN (American Registry for Internet Numbers) is a Regional Internet Registry responsible for managing and distributing IP address space and related resources in North America and parts of the Caribbean.
-
B.
AFRINIC
AFRINIC is the Regional Internet Registry responsible for allocating and managing IP address resources across the African region.
-
C.
RIPE NCC
RIPE NCC is the Regional Internet Registry for Europe, the Middle East, and parts of Central Asia, responsible for allocating and registering IP address space and related Internet number resources.
-
D.
APNIC
APNIC is the Regional Internet Registry responsible for allocating and managing IP address resources in the Asia-Pacific region.
-
E.
Regional Internet Registries
Regional Internet Registries are organizations responsible for allocating and managing IP address space and related Internet number resources within specific geographic regions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3c415f83c8190b95755f23faae026 |
completed | March 1, 2026, 4:44 a.m. |
Created at: Feb. 28, 2026, 1:06 p.m.