Triple
T35858065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magellan |
E1036561
|
entity |
| Predicate | mappedSurfaceCoverage |
P1987
|
FINISHED |
| Object | over 98 percent of Venus surface |
—
|
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: over 98 percent of Venus surface | Statement: [Magellan, mappedSurfaceCoverage, over 98 percent of Venus surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mappedSurfaceCoverage Context triple: [Magellan, mappedSurfaceCoverage, over 98 percent of Venus surface]
-
A.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
B.
mapCoverage
chosen
Indicates the extent or area that is represented, covered, or included by a particular map.
-
C.
sensorCoverage
Indicates that a sensor’s detection or monitoring area spatially covers or includes a given region, object, or point.
-
D.
scaleCoverage
Indicates adjusting the extent or scope of coverage, typically by increasing or decreasing it according to some scale or demand.
-
E.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.