Triple
T29257353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet protocol parameter assignments |
E741737
|
entity |
| Predicate | includesRegistry |
P200604
|
FINISHED |
| Object | IP protocol numbers registry |
—
|
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: IP protocol numbers registry | Statement: [Internet protocol parameter assignments, includesRegistry, IP protocol numbers registry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRegistry Context triple: [Internet protocol parameter assignments, includesRegistry, IP protocol numbers registry]
-
A.
includesResources
Indicates that one entity contains, encompasses, or makes available specific resources as part of its composition or offering.
-
B.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
-
C.
includesMap
Indicates that one entity contains or incorporates another entity in the form of a map or mapping structure.
-
D.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
| PDg | Predicate description generation | batch_69ff9b19f254819099bb9c034d2b399b |
completed | May 9, 2026, 8:37 p.m. |
Created at: April 28, 2026, 12:38 p.m.