Triple
T20446836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucana II |
E501537
|
entity |
| Predicate | hasStars |
P140144
|
FINISHED |
| Object | extremely metal-poor stars |
—
|
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: extremely metal-poor stars | Statement: [Tucana II, hasStars, extremely metal-poor stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStars Context triple: [Tucana II, hasStars, extremely metal-poor stars]
-
A.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
B.
starIs
Indicates that one entity is identified or classified as a star in relation to another entity or context.
-
C.
starCount
Indicates the number of stars associated with an entity, typically representing a rating, quality level, or count of starred items.
-
D.
hasBrightStar
Indicates that one entity possesses, contains, or is associated with a star characterized by high brightness.
-
E.
hasSiblingStars
Indicates that two or more stars share at least one common parent system or origin, making them siblings in an astrophysical or formation context.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68cfe57a8819094bd3d324bd567f5 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:32 a.m.