Triple
T19932157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rasalhague |
E479080
|
entity |
| Predicate | isInBinarySystem |
P56529
|
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: [Rasalhague, isInBinarySystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInBinarySystem Context triple: [Rasalhague, isInBinarySystem, true]
-
A.
isInSystem
Indicates that one entity is located within, belongs to, or is contained by a particular system.
-
B.
isEclipsingBinary
Indicates that two stars form a binary system whose orbital plane is aligned so that, from the observer’s viewpoint, one periodically passes in front of the other, causing observable eclipses in brightness.
-
C.
hasBinaryPeriod
Indicates that two objects in a binary system have a specific orbital period for completing one full revolution around their common center of mass.
-
D.
hasBinary
chosen
Indicates that one entity is associated with another entity in a binary (two-component) relationship, typically as one of the two members of a pair.
-
E.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.