Triple
T18695667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crab Nebula |
E457107
|
entity |
| Predicate | associatedWithHistoricalRecord |
P85795
|
FINISHED |
| Object | guest star of 1054 |
—
|
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: guest star of 1054 | Statement: [Crab Nebula, associatedWithHistoricalRecord, guest star of 1054]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHistoricalRecord Context triple: [Crab Nebula, associatedWithHistoricalRecord, guest star of 1054]
-
A.
associatedWithHistoricalState
Indicates that an entity has a relationship or connection to a specific historical state or former political entity.
-
B.
associatedWithHistoricSee
Indicates that an entity has a formal or traditional connection to a particular historic episcopal see or ecclesiastical jurisdiction.
-
C.
historicalRecord
chosen
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
D.
associatedWithHistoricHome
Indicates a relationship in which an entity is connected or linked in some relevant way to a historic home.
-
E.
associatedWithLegacy
Indicates that an entity has a connection or linkage to something from the past, such as historical versions, prior systems, or inherited artifacts.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.