Triple
T29030715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBP Broadcast |
E737719
|
entity |
| Predicate | addressResolutionType |
P23644
|
FINISHED |
| Object | name-to-address resolution |
—
|
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: name-to-address resolution | Statement: [NBP Broadcast, addressResolutionType, name-to-address resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressResolutionType Context triple: [NBP Broadcast, addressResolutionType, name-to-address resolution]
-
A.
addressMappingType
chosen
Indicates the specific way in which one address is associated with, translated to, or mapped onto another address or address space.
-
B.
addressAssignmentType
Indicates the manner or category by which an address is designated or assigned to an entity.
-
C.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
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.
addressRepresents
Indicates that one address stands for, corresponds to, or serves as the official representation of another entity or location.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 9:55 a.m.