Triple
T5201982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SagDEG |
E117412
|
entity |
| Predicate | usedAsTracerFor |
P2506
|
FINISHED |
| Object | Milky Way dark matter halo shape |
—
|
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: Milky Way dark matter halo shape | Statement: [SagDEG, usedAsTracerFor, Milky Way dark matter halo shape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTracerFor Context triple: [SagDEG, usedAsTracerFor, Milky Way dark matter halo shape]
-
A.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
B.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
C.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
D.
traceWithRespectTo
Indicates that one entity records, follows, or monitors the behavior, changes, or effects of another entity relative to a specified reference or context.
-
E.
usedInDetector
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.