Triple
T1309008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna |
E27944
|
entity |
| Predicate | nodePrecessionPeriod |
P27812
|
FINISHED |
| Object | about 18.6 years |
—
|
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 18.6 years | Statement: [Luna, nodePrecessionPeriod, about 18.6 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nodePrecessionPeriod Context triple: [Luna, nodePrecessionPeriod, about 18.6 years]
-
A.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
endDateSidereal
Indicates the date and time, measured in sidereal rather than solar terms, at which a specified event, state, or interval comes to an end.
-
C.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
D.
startDateSidereal
Indicates the sidereal (star-based) date on which an event, period, or state begins.
-
E.
longitudeOfAscendingNode
Indicates the angular position of an orbit’s ascending node measured from a reference direction in the reference plane.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c15361c8819094b8171e780b5560 |
completed | March 1, 2026, 10:44 p.m. |
Created at: March 1, 2026, 7:51 p.m.