Triple
T10023374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planetary Hypotheses |
E200664
|
entity |
| Predicate | places |
P91762
|
FINISHED |
| Object | fixed stars on outermost sphere |
—
|
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: fixed stars on outermost sphere | Statement: [Planetary Hypotheses, places, fixed stars on outermost sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: places Context triple: [Planetary Hypotheses, places, fixed stars on outermost sphere]
-
A.
placeType
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
B.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
C.
placesInQuestion
Indicates that an entity is located within, or occurs in, the spatial or contextual scope defined by a given question.
-
D.
cities
Indicates a relationship where one or more entities are identified as cities associated with another entity (such as a country, region, or person).
-
E.
promotionPlaces
Indicates that one entity designates or assigns another entity to a higher position, rank, or status within some organizational or hierarchical structure.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7c75548190aa604d90d63dc111 |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:53 p.m.