Triple
T20327162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WASP-72 |
E492367
|
entity |
| Predicate | epochOfExoplanetDiscovery |
P3836
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [WASP-72, epochOfExoplanetDiscovery, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epochOfExoplanetDiscovery Context triple: [WASP-72, epochOfExoplanetDiscovery, 2012]
-
A.
perihelionYear
Indicates the specific calendar year in which an object's orbit brings it to perihelion, its closest point to the Sun.
-
B.
discoveryDate
chosen
Indicates the date on which something was first discovered or identified.
-
C.
hasExoplanetsDetected
Indicates that one or more exoplanets have been observed and confirmed to exist in association with the referenced astronomical object.
-
D.
earthDayLengthening_rateMillisecondsPerCentury
Indicates the rate at which the length of an Earth day increases, measured in milliseconds per century.
-
E.
hasNumberOfConfirmedPlanets
Indicates the relationship that specifies how many planets within a given system or context have been confirmed to exist.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.