Triple
T1899851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Meteorological Telecommunication Network |
E37666
|
entity |
| Predicate | servesUser |
P14200
|
FINISHED |
| Object | national weather forecasting centers |
—
|
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: national weather forecasting centers | Statement: [National Meteorological Telecommunication Network, servesUser, national weather forecasting centers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesUser Context triple: [National Meteorological Telecommunication Network, servesUser, national weather forecasting centers]
-
A.
servesUsers
chosen
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
D.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
E.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb18c46c88190b10c05bf5c6a2d9c |
completed | March 7, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.