Triple
T4402490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X.25 |
E93647
|
entity |
| Predicate | hasAddressingScheme |
P1216
|
FINISHED |
| Object | X.121 |
—
|
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: X.121 | Statement: [X.25, hasAddressingScheme, X.121]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddressingScheme Context triple: [X.25, hasAddressingScheme, X.121]
-
A.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
B.
usesAddressingSystem
chosen
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
C.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
D.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
-
E.
hasRouteNumberingScheme
Indicates that one entity uses or is assigned a particular system or scheme for numbering its routes.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d08a0c8190ac6c125df40eca75 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.