Triple
T11164857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | actinide series |
E264133
|
entity |
| Predicate | hasPeriodRange |
P98199
|
FINISHED |
| Object | period 7 |
—
|
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: period 7 | Statement: [actinide series, hasPeriodRange, period 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodRange Context triple: [actinide series, hasPeriodRange, period 7]
-
A.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
B.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
includesPeriodFeature
Indicates that something contains or incorporates a specific period-related feature as part of its characteristics or structure.
-
E.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
- F. None of above. chosen
Provenance (4 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e887293081909830852000d533fa |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.