Triple
T2173784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London penetration depth |
E48480
|
entity |
| Predicate | isLargerFor |
P10621
|
FINISHED |
| Object | dirty or disordered superconductors |
—
|
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: dirty or disordered superconductors | Statement: [London penetration depth, isLargerFor, dirty or disordered superconductors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargerFor Context triple: [London penetration depth, isLargerFor, dirty or disordered superconductors]
-
A.
largerThan
chosen
Indicates that one entity has a greater size, extent, or magnitude than another entity.
-
B.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
C.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
-
D.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
-
E.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.