Triple
T1180614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albedo 0.39 |
E25126
|
entity |
| Predicate | hasKeyTrack |
P9942
|
FINISHED |
| Object | Pulstar |
—
|
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: Pulstar | Statement: [Albedo 0.39, hasKeyTrack, Pulstar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyTrack Context triple: [Albedo 0.39, hasKeyTrack, Pulstar]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
-
C.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
D.
ownerOfSomeTrack
chosen
Indicates that an entity has ownership of at least one track (such as a song, audio track, or similar item).
-
E.
hasKeyFigure
Indicates that an entity includes, involves, or is characterized by an important or central person relevant to it.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd32c5f48190b4e2d39fa052cbb7 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.