Triple
T34378856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Highway 13 |
E882370
|
entity |
| Predicate | hasNetworkNumber |
P200995
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Asian Highway 13, hasNetworkNumber, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkNumber Context triple: [Asian Highway 13, hasNetworkNumber, 13]
-
A.
hasNetworkName
Indicates that an entity is associated with a specific network identifier or name.
-
B.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
C.
hasNetworkSize
Indicates the total number of nodes, members, or connections that make up a given network.
-
D.
hasNetworkSignificance
Indicates that an entity holds importance, influence, or a critical role within a network or interconnected system.
-
E.
hasIP
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
| PDg | Predicate description generation | batch_69ffc082a4e881908a92313d2c755afe |
completed | May 9, 2026, 11:17 p.m. |
Created at: May 1, 2026, 1:59 a.m.