Triple
T25638391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helike |
E642768
|
entity |
| Predicate | orbitalCharacter |
P58578
|
FINISHED |
| Object | distant |
—
|
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: distant | Statement: [Helike, orbitalCharacter, distant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalCharacter Context triple: [Helike, orbitalCharacter, distant]
-
A.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
B.
orbitalComponent
Indicates that one entity is a component or part of another entity’s orbital system or orbital structure.
-
C.
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.
-
D.
orbitalAssociation
Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another object.
-
E.
orbitalPosition
Indicates the relative location or path of one object in its orbit with respect to a central body or reference frame.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 5:37 p.m.