Triple
T16431248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tropical Rainfall Measuring Mission |
E399074
|
entity |
| Predicate | coverageRegion |
P19200
|
FINISHED |
| Object | tropical regions |
—
|
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: tropical regions | Statement: [Tropical Rainfall Measuring Mission, coverageRegion, tropical regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverageRegion Context triple: [Tropical Rainfall Measuring Mission, coverageRegion, tropical regions]
-
A.
campaignRegion
Indicates the geographic area or territory in which a campaign is conducted or targeted.
-
B.
regionCoverage
chosen
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
C.
countyRegion
Indicates that a county is located within, or is administratively part of, a larger geographic region.
-
D.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
E.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9dffe48190a23852f828af55d8 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.