Triple
T18772802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbig Ae/Be stars |
E459056
|
entity |
| Predicate | HRDiagramLocation |
P132920
|
FINISHED |
| Object | above the main sequence |
—
|
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: above the main sequence | Statement: [Herbig Ae/Be stars, HRDiagramLocation, above the main sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HRDiagramLocation Context triple: [Herbig Ae/Be stars, HRDiagramLocation, above the main sequence]
-
A.
positionInAsterism
Indicates the specific location or role that an object occupies within a defined asterism pattern.
-
B.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
-
C.
starPosition
Indicates the spatial location or coordinates of a star relative to a defined reference frame.
-
D.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
E.
chartPosition
Indicates the ranking or placement of an item within an ordered chart or list at a specific point in time.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.