Triple
T5259596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proteus (moon) |
E118790
|
entity |
| Predicate | rotationalPeriod |
P2026
|
FINISHED |
| Object | about 1.122 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 1.122 days | Statement: [Proteus (moon), rotationalPeriod, about 1.122 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationalPeriod Context triple: [Proteus (moon), rotationalPeriod, about 1.122 days]
-
A.
hasRotationPeriod
chosen
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
-
B.
timeInOrbit_days
Indicates the number of days an object has spent in orbit around a celestial body.
-
C.
isTidallyLockedTo
Indicates that one object's rotational period matches its orbital period around another object, so the same side always faces that other object.
-
D.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
E.
isTidallyLockedWith
Indicates that two astronomical bodies always show the same face to each other because one’s rotation period matches its orbital period around the other.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.