Triple
T934107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perseus Arm |
E20156
|
entity |
| Predicate | tracedBy |
P11414
|
FINISHED |
| Object | radio observations of neutral hydrogen |
—
|
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: radio observations of neutral hydrogen | Statement: [Perseus Arm, tracedBy, radio observations of neutral hydrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tracedBy Context triple: [Perseus Arm, tracedBy, radio observations of neutral hydrogen]
-
A.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
B.
tracesTo
chosen
Indicates a relationship where one item can be followed or linked back as the origin, source, or cause of another.
-
C.
traceWithRespectTo
Indicates that one entity records, follows, or monitors the behavior, changes, or effects of another entity relative to a specified reference or context.
-
D.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
E.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b299c4d881908a57ac2711676cd7 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.