Triple
T18950810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neptunium |
E463642
|
entity |
| Predicate | corrodesIn |
P133921
|
FINISHED |
| Object | air |
—
|
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: air | Statement: [neptunium, corrodesIn, air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corrodesIn Context triple: [neptunium, corrodesIn, air]
-
A.
isCorrosionResistantWhen
Indicates that an entity remains resistant to corrosion under specified conditions or circumstances.
-
B.
isCorrosionResistantInAir
Indicates that an entity maintains its integrity and does not significantly corrode when exposed to air under specified conditions.
-
C.
corrupts
Indicates that one entity causes another entity, system, or process to become morally, functionally, or structurally degraded or impaired.
-
D.
eroded
Indicates that a force or process has gradually worn away, diminished, or degraded something over time.
-
E.
hasErosionEffect
Indicates that one entity causes or exhibits an erosive impact or degradation effect on another entity or surface.
- F. None of above. chosen
Provenance (4 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d542b238819089ccd2df279a2f7f |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon