Triple
T5990711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philolaus |
E133339
|
entity |
| Predicate | cosmicBodies |
P67864
|
FINISHED |
| Object | central fire |
—
|
LITERAL FINISHED |
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: central fire | Statement: [Philolaus, cosmicBodies, central fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicBodies Context triple: [Philolaus, cosmicBodies, central fire]
-
A.
majorBody
Indicates that one entity is the primary or most significant body (e.g., celestial, organizational, or governing body) in relation to another entity.
-
B.
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).
-
C.
orbitsBeyond
Indicates that one celestial body orbits at a greater average distance from a central object than another specified body.
-
D.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
E.
astronomicalSystem
Indicates a relationship in which multiple astronomical objects are organized into a coherent physical or dynamical system (such as a planetary system, star system, or galaxy).
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc8ab648190beb1bc141796894e |
completed | March 22, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:05 p.m.