Triple
T34911909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WASP-39b |
E1006894
|
entity |
| Predicate | orbitalPeriodUnit |
P182101
|
FINISHED |
| Object | day |
—
|
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: day | Statement: [WASP-39b, orbitalPeriodUnit, day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalPeriodUnit Context triple: [WASP-39b, orbitalPeriodUnit, day]
-
A.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
timeInOrbit_days
Indicates the number of days an object has spent in orbit around a celestial body.
-
C.
orbitalPeriodRange_minutesUpperBound
Indicates the maximum value, in minutes, of the allowed or observed range for an entity’s orbital period.
-
D.
epochOfOrbit
Indicates the specific reference time at which an orbit’s parameters are defined or measured.
-
E.
orbitalPeriodRange_minutesLowerBound
Indicates the minimum value of an object's orbital period, expressed in minutes, within a specified range.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4 p.m.