Triple
T3158644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | type-I superconductors |
E66049
|
entity |
| Predicate | haveParameter |
P4452
|
FINISHED |
| Object | penetration depth lambda |
—
|
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: penetration depth lambda | Statement: [type-I superconductors, haveParameter, penetration depth lambda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveParameter Context triple: [type-I superconductors, haveParameter, penetration depth lambda]
-
A.
hasParameter
chosen
Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
hasDimensionParameter
Indicates that an entity is associated with a specific dimensional parameter (such as size, length, width, or height) that characterizes its measurable extent.
-
D.
hasParType
Indicates that an entity has a specific parent type or category to which it belongs.
-
E.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ed82a08190a1bdcf18ee593c79 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.