Triple
T869974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Sisters |
E18787
|
entity |
| Predicate | isBrightestOpenClusterIn |
P20404
|
FINISHED |
| Object | northern sky |
—
|
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: northern sky | Statement: [Seven Sisters, isBrightestOpenClusterIn, northern sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBrightestOpenClusterIn Context triple: [Seven Sisters, isBrightestOpenClusterIn, northern sky]
-
A.
brightestStar
Indicates that one entity is the most luminous star within a specified group, region, or context relative to the others.
-
B.
brightestStarApparentMagnitude
Indicates the apparent brightness value (magnitude) of the brightest star as seen from a given observation point.
-
C.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
-
D.
apparentMagnitude
Indicates the observed brightness of an astronomical object as seen from Earth, on a logarithmic scale where lower values correspond to brighter appearances.
-
E.
relatedConstellation
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac811e548190a72b7a10b5ea8665 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.