Triple
T19377008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La2CuO4 |
E484697
|
entity |
| Predicate | discoveredAsParentOf |
P25799
|
FINISHED |
| Object | La2−xBaxCuO4 superconductor |
—
|
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: La2−xBaxCuO4 superconductor | Statement: [La2CuO4, discoveredAsParentOf, La2−xBaxCuO4 superconductor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredAsParentOf Context triple: [La2CuO4, discoveredAsParentOf, La2−xBaxCuO4 superconductor]
-
A.
isParentOf
Indicates that one entity is the biological or legal parent of another entity.
-
B.
discoveredAsPartOf
Indicates that something was found, identified, or revealed in the course of a larger activity, process, or investigation of which it formed a component.
-
C.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
D.
discoveredAs
chosen
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
E.
usedAsParentFor
Indicates that one entity functions as the parent or container for another entity within a hierarchical or structural 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5cfbf48190ac60e3ffa6baa263 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.