Triple
T13180006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanth |
E313696
|
entity |
| Predicate | hasOrbitalConfiguration |
P58578
|
FINISHED |
| Object | close binary with Orcus |
—
|
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: close binary with Orcus | Statement: [Vanth, hasOrbitalConfiguration, close binary with Orcus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalConfiguration Context triple: [Vanth, hasOrbitalConfiguration, close binary with Orcus]
-
A.
hasElectronConfiguration
Indicates that an entity (typically an atom or ion) possesses a specific arrangement of electrons in its atomic orbitals.
-
B.
hasOrbitalSignature
Indicates that one entity possesses or is characterized by a distinctive orbital pattern or trajectory associated with another entity.
-
C.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
-
D.
hasOrbitalCharacteristic
chosen
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
E.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.