Triple
T35023136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon Lagrange region |
E1010249
|
entity |
| Predicate | hasStablePoint |
P201118
|
FINISHED |
| Object | Earth–Moon L4 point |
—
|
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: Earth–Moon L4 point | Statement: [Earth–Moon Lagrange region, hasStablePoint, Earth–Moon L4 point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStablePoint Context triple: [Earth–Moon Lagrange region, hasStablePoint, Earth–Moon L4 point]
-
A.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
B.
hasFixedPoint
Indicates that a function or mapping has at least one input value that is mapped to itself as output.
-
C.
isConditionallyStable
Indicates that an entity remains stable only under certain specified conditions or constraints.
-
D.
isStableUnder
Indicates that a property, structure, or condition remains unchanged when a specified operation, transformation, or perturbation is applied.
-
E.
haveStabilityDeterminedBy
Indicates that the stability of one entity is determined or governed by another specified factor or entity.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ffc894cef481908dae1d9cdc7d9d1f |
completed | May 9, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:01 p.m.