Triple
T20480384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GD-1 stream |
E502434
|
entity |
| Predicate | isCandidateProbeFor |
P23055
|
FINISHED |
| Object | dark matter subhalos |
—
|
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: dark matter subhalos | Statement: [GD-1 stream, isCandidateProbeFor, dark matter subhalos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCandidateProbeFor Context triple: [GD-1 stream, isCandidateProbeFor, dark matter subhalos]
-
A.
isUsedToProbe
chosen
Indicates that one entity is employed as a tool or method to investigate, test, or explore the properties, behavior, or state of another entity.
-
B.
isCandidate
Indicates that an entity is being considered or put forward for a particular position, role, or selection process.
-
C.
candidateFor
Indicates that one entity is being considered or proposed as a possible choice, option, or selection for another entity (such as a role, position, or outcome).
-
D.
hasCandidatePlanet
Indicates that an object (typically a star or system) is associated with a planet that is suspected or proposed to exist but not yet fully confirmed.
-
E.
isPro
Indicates that an entity is a professional or expert in a particular field, activity, or domain.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b55d7a881909dfe3ea0e74b742b |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:34 a.m.