Triple
T6287146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 87 Tauri |
E140927
|
entity |
| Predicate | hasLuminositySolar |
P7281
|
FINISHED |
| Object | about 50 |
—
|
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: about 50 | Statement: [87 Tauri, hasLuminositySolar, about 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuminositySolar Context triple: [87 Tauri, hasLuminositySolar, about 50]
-
A.
luminosityRelativeToSun
chosen
Indicates how bright an object is compared to the Sun, expressed as a ratio of their luminosities.
-
B.
hasMaximumSolarInsolation
Indicates that an entity receives the highest level of solar radiation or sunlight intensity compared to relevant alternatives or within a given context.
-
C.
hasMinimumSolarInsolation
Indicates that an entity receives at least a specified minimum amount of solar energy (insolation) over a given area and time period.
-
D.
hasRelationToSun
Indicates a relationship in which an entity is connected or related in some way to the Sun.
-
E.
hasSolarDayLength
Indicates that an entity is associated with a specific duration for one complete solar day (the time between successive noons).
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063ff9f74819088dc603f56fc930c |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.