Triple
T30962024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GL16 |
E788852
|
entity |
| Predicate | hasAddressFormatElement |
P23479
|
FINISHED |
| Object | outward code GL16 |
—
|
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: outward code GL16 | Statement: [GL16, hasAddressFormatElement, outward code GL16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddressFormatElement Context triple: [GL16, hasAddressFormatElement, outward code GL16]
-
A.
hasFormatElement
chosen
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
B.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
C.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
D.
hasAddressRole
Indicates that a specific role or function is associated with an address within a given context (e.g., billing, shipping, primary).
-
E.
hasFormatSpecification
Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 29, 2026, 8:54 p.m.