Triple
T29542074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavlov B |
E749528
|
entity |
| Predicate | belongsToPlanetaryBody |
P70604
|
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: [Pavlov B, belongsToPlanetaryBody, Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToPlanetaryBody Context triple: [Pavlov B, belongsToPlanetaryBody, Moon]
-
A.
associatedWithCelestialBody
chosen
Indicates a relationship in which an entity has a connection, link, or relevance to a specific celestial body (such as a planet, star, or moon).
-
B.
planetaryBodyContext
Indicates a contextual relationship in which one planetary body is considered or analyzed relative to another body, system, or environment (e.g., its orbital, spatial, or situational setting).
-
C.
isInPlanetarySystem
Indicates that one celestial object is located within and belongs to a particular planetary system.
-
D.
inSolarSystemBody
Indicates that one entity is located within, on, or as part of a specified solar system body (such as a planet, moon, or asteroid).
-
E.
hasCentralBodyRole
Indicates that an entity serves as the primary or central functional component within a larger body or system.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 28, 2026, 5:03 p.m.