Triple
T18842969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta Sagittarii |
E460841
|
entity |
| Predicate | hasMultipleStarComponents |
P69238
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zeta Sagittarii, hasMultipleStarComponents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleStarComponents Context triple: [Zeta Sagittarii, hasMultipleStarComponents, true]
-
A.
containsStarType
Indicates that one entity includes or is associated with a star of a specified stellar type.
-
B.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
C.
isMultipleStarSystem
chosen
Indicates that a star system contains two or more stars gravitationally bound together, rather than a single isolated star.
-
D.
hasMultipleSegments
Indicates that the referenced entity is composed of more than one distinct segment or section.
-
E.
isResolvedIntoIndividualStars
Indicates that an object or region, previously appearing as a single source, can be distinguished into its constituent individual stars.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.