Triple
T23527783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpens |
E576478
|
entity |
| Predicate | hasIAUBoundaryDefinitionYear |
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: [Serpens, hasIAUBoundaryDefinitionYear, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIAUBoundaryDefinitionYear Context triple: [Serpens, hasIAUBoundaryDefinitionYear, 1930]
-
A.
hasIAUBoundariesDefinedBy
Indicates that an entity’s boundaries are defined or delimited according to standards or specifications established by the International Astronomical Union (IAU).
-
B.
definedInYear
chosen
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
-
C.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
-
D.
hasDefinedBoundaries
Indicates that the entity possesses clearly established and recognized limits or borders that distinguish it from its surroundings or from other entities.
-
E.
hasOverrulingYear
Indicates the year in which a prior decision, rule, or action was formally overruled or invalidated.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac758038819098f5f597be39274e |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.