Triple
T35023125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon Lagrange region |
E1010249
|
entity |
| Predicate | hasSecondaryBody |
P90082
|
FINISHED |
| Object | Moon |
—
|
NE NERFINISHED |
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: Moon | Statement: [Earth–Moon Lagrange region, hasSecondaryBody, Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryBody Context triple: [Earth–Moon Lagrange region, hasSecondaryBody, Moon]
-
A.
hasNaturalSatellite
Indicates that one celestial body is orbited by another body that occurs naturally as its satellite.
-
B.
isLagrangianSatelliteOf
Indicates that one celestial body occupies a Lagrangian point and thus functions as a gravitationally bound satellite associated with another primary body.
-
C.
isSecondLargestMoonOf
Indicates that one celestial body is the second largest moon in size orbiting a specified primary body.
-
D.
hasNumberOfKnownMoons
Indicates the relationship that specifies how many moons are known to orbit a given celestial body.
-
E.
hasSecondary
chosen
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:01 p.m.