Triple
T37532964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | σ Herculis |
E933108
|
entity |
| Predicate | hasCloseOrbit |
P195957
|
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: [σ Herculis, hasCloseOrbit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloseOrbit Context triple: [σ Herculis, hasCloseOrbit, true]
-
A.
hasOrbit
Indicates that one entity follows a curved, typically gravitationally bound path around another entity.
-
B.
hasAxisOfOrbit
Indicates that an orbiting object is associated with a specific axis around which its orbital motion is defined.
-
C.
isOrbitalAround
Indicates that one entity moves in a stable, curved path (orbit) around another entity due to gravitational or similar central forces.
-
D.
hasHeliocentricOrbit
Indicates that an object follows an orbital path around the Sun as its central body.
-
E.
hasOrbitCrossing
Indicates that the orbital path of one celestial body intersects or crosses the orbital path of another.
- F. None of above. chosen
Provenance (4 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:17 p.m.