Triple
T18552144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassiopeia |
E453402
|
entity |
| Predicate | IAUBoundaryDefinitionYear |
P98236
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [Cassiopeia, IAUBoundaryDefinitionYear, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IAUBoundaryDefinitionYear Context triple: [Cassiopeia, IAUBoundaryDefinitionYear, 1930]
-
A.
definedInYear
chosen
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
-
B.
hasIAUBoundariesDefinedBy
Indicates that an entity’s boundaries are defined or delimited according to standards or specifications established by the International Astronomical Union (IAU).
-
C.
integratedYear
Indicates the year in which one entity was incorporated into, merged with, or formally added to another entity or system.
-
D.
yearType
Indicates the classification or category assigned to a specific year (e.g., academic, fiscal, calendar, leap).
-
E.
endBoundaryDefinedBy
Indicates that the endpoint or final limit of one entity is determined, marked, or delimited by 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538019a74819099dbd255fb21fa95 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.