Triple
T654191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Backbone of Night |
E11609
|
entity |
| Predicate | titleRefersTo |
P4929
|
FINISHED |
| Object | the Milky Way as seen in the night sky |
—
|
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: the Milky Way as seen in the night sky | Statement: [The Backbone of Night, titleRefersTo, the Milky Way as seen in the night sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRefersTo Context triple: [The Backbone of Night, titleRefersTo, the Milky Way as seen in the night sky]
-
A.
titleAlludesTo
chosen
Indicates that one title makes an indirect or suggestive reference to the content, theme, or another work associated with the other.
-
B.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
C.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
D.
titleDerivedFrom
Indicates that the title of one entity is obtained or adapted from another entity.
-
E.
title
Indicates that one entity serves as the formal name or designation of another entity.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4bb5b881908a18b5ec1c94e0cf |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.