Triple
T18775585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bright Star Catalogue |
E459124
|
entity |
| Predicate | magnitudeLimit |
P16655
|
FINISHED |
| Object | about visual magnitude 6.5 |
—
|
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: about visual magnitude 6.5 | Statement: [Bright Star Catalogue, magnitudeLimit, about visual magnitude 6.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magnitudeLimit Context triple: [Bright Star Catalogue, magnitudeLimit, about visual magnitude 6.5]
-
A.
gLimit
chosen
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
B.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
C.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
D.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
E.
dimensionRestriction
Indicates a constraint or limit imposed on the size, extent, or number of dimensions associated with an entity or relationship.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933ad4288190b17e5fad57d8417d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.