Triple
T34975927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi |
E1008675
|
entity |
| Predicate | hasDegradationState |
P139016
|
FINISHED |
| Object | heavily degraded |
—
|
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: heavily degraded | Statement: [Fermi, hasDegradationState, heavily degraded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDegradationState Context triple: [Fermi, hasDegradationState, heavily degraded]
-
A.
hasStateOf
Indicates that an entity possesses, exhibits, or is currently in a particular condition, status, or mode.
-
B.
hasErosionalState
chosen
Indicates the current degree or condition of erosion affecting an entity’s surface or structure.
-
C.
hasPerceptualQuality
Indicates that something possesses a particular sensory or perceptual characteristic, such as a color, sound, texture, taste, or smell.
-
D.
mayBeDowngradedTo
Indicates that one entity has the potential or permission to be reduced in status, level, or classification to another entity.
-
E.
degradationMechanism
Indicates the process or mechanism by which something deteriorates, breaks down, or loses its original quality or function over time.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:01 p.m.