Triple
T32224581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilion |
E823159
|
entity |
| Predicate | cosmicBody |
P67864
|
FINISHED |
| Object | Isil (the 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: Isil (the Moon) | Statement: [Tilion, cosmicBody, Isil (the Moon)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicBody Context triple: [Tilion, cosmicBody, Isil (the Moon)]
-
A.
cosmicBodies
chosen
Indicates a relationship in which entities are identified as astronomical or celestial objects existing in outer space.
-
B.
majorBody
Indicates that one entity is the primary or most significant body (e.g., celestial, organizational, or governing body) in relation to another entity.
-
C.
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).
-
D.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
E.
observedAstronomicalBody
Indicates that an entity has observed, detected, or recorded data about a particular astronomical body.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbc8c6c881908ce99e774c010ff5 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:38 a.m.