Triple
T6534233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lanthanides |
E152311
|
entity |
| Predicate | hasAtomicNumberRange |
P27293
|
FINISHED |
| Object | 57–71 |
—
|
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: 57–71 | Statement: [lanthanides, hasAtomicNumberRange, 57–71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAtomicNumberRange Context triple: [lanthanides, hasAtomicNumberRange, 57–71]
-
A.
hasAtomicNumber
Indicates that one entity is the chemical element whose atomic number (number of protons in its nucleus) is given by the other entity.
-
B.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
hasAtomicRadius
Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
-
D.
hasProtonNumber
Indicates that an entity (typically a chemical element or atom) possesses a specific number of protons in its nucleus.
-
E.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbf3a748190b0fb52122faaf6d3 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.