Triple
T21652139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Correios |
E534363
|
entity |
| Predicate | hasNetworkComponent |
P118177
|
FINISHED |
| Object | post offices |
—
|
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: post offices | Statement: [Correios, hasNetworkComponent, post offices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkComponent Context triple: [Correios, hasNetworkComponent, post offices]
-
A.
hasNetworkElement
chosen
Indicates that one entity includes, contains, or is associated with a specific network element as part of its network structure or configuration.
-
B.
hasNetworkStructure
Indicates that one entity possesses, exhibits, or is organized according to a particular network-based structure defined by another entity or specification.
-
C.
hasServerComponent
Indicates that an entity includes, depends on, or is associated with a particular server-side component.
-
D.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
E.
hasNetworkName
Indicates that an entity is associated with a specific network identifier or name.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef591594a08190bf0ddd0a0c0922ba |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.