Triple
T34543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth |
E687
|
entity |
| Predicate | hasOrbitalPeriod |
P2028
|
FINISHED |
| Object | about 365.25 days |
—
|
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: about 365.25 days | Statement: [Earth, hasOrbitalPeriod, about 365.25 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalPeriod Context triple: [Earth, hasOrbitalPeriod, about 365.25 days]
-
A.
hasPeakUsageInHemisphere
Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
spaceProgram
Indicates that an entity is involved in, operates, or is associated with an organized program dedicated to space exploration, research, or related activities.
-
D.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
E.
legislativePeriodicity
Indicates how frequently a legislative body or process recurs or is scheduled to occur over time.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a24872e4e481908567850168d65015 |
completed | Feb. 28, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69a248fef2b881908180bd4e32e58cb5 |
completed | Feb. 28, 2026, 1:46 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.