Triple
T34484332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnox |
E885275
|
entity |
| Predicate | claddingLimitation |
P99
|
FINISHED |
| Object | poor corrosion resistance in water |
—
|
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: poor corrosion resistance in water | Statement: [Magnox, claddingLimitation, poor corrosion resistance in water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claddingLimitation Context triple: [Magnox, claddingLimitation, poor corrosion resistance in water]
-
A.
claddingName
Indicates the specific name or designation assigned to a cladding material or system used on a structure.
-
B.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
C.
showsLimitationOf
Indicates that one entity reveals, demonstrates, or makes apparent the limitations, weaknesses, or constraints of another entity.
-
D.
appliesToCliff
Indicates that an action, condition, or rule is specifically relevant or directed toward a cliff.
-
E.
dimensionRestriction
Indicates a constraint or limit imposed on the size, extent, or number of dimensions associated with an entity or relationship.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:01 a.m.