Triple
T29211881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budhan |
E740566
|
entity |
| Predicate | correspondsToPlanet |
P52435
|
FINISHED |
| Object | Mercury |
—
|
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: Mercury | Statement: [Budhan, correspondsToPlanet, Mercury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToPlanet Context triple: [Budhan, correspondsToPlanet, Mercury]
-
A.
associatedPlanet
chosen
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
-
B.
appearsOnPlanetNumber
Indicates that an entity is depicted or present on a specific planet identified by its ordinal number in a sequence.
-
C.
isPlanet
Indicates that the subject entity is classified as a planet.
-
D.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
E.
associatedWithCelestialBody
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).
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 12:11 p.m.