Triple
T5479411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS64 |
E123433
|
entity |
| Predicate | prefixExample |
P23640
|
FINISHED |
| Object | 64:ff9b::/96 |
—
|
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: 64:ff9b::/96 | Statement: [DNS64, prefixExample, 64:ff9b::/96]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefixExample Context triple: [DNS64, prefixExample, 64:ff9b::/96]
-
A.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
B.
addressPrefix
chosen
Indicates that one address string serves as the starting portion or leading segment of another address.
-
C.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
D.
prefixAssignedBy
Indicates that a specific prefix has been designated or allocated to an entity by a particular assigning authority or agent.
-
E.
standardPrefix
Indicates that one entity serves as the conventional or officially recognized prefix used before another 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.